Summary rollover date
I thought we'd switched to a Monday deadline for the summary and a Sunday night roll over. I just noticed your last summary ended on a Monday night. -- Piers Cawley [EMAIL PROTECTED] http://www.bofh.org.uk/
Re: loadlib and libraries with '.' in the name
Joshua Juran [EMAIL PROTECTED] writes: On Sep 23, 2005, at 3:47 AM, Leopold Toetsch wrote: On Sep 23, 2005, at 7:51, Ross McFarland wrote: i was planning on playing around with gtk+ bindings and parrot and went about looking around for the work that had already been done and didn't turn anything up. if anyone knows where i can find it or who i should talk to i would appreciate that info as well. Google for NCI gtk. There is also a weekly summary entry but the xrl.us shortcut seems to have expired. I was wondering about that. I Googled for tinyurl considered harmful and was surprised to find only one message, discussing the phishing risks. I found no mention of the risk of outsourcing a bottleneck to a third party who has zero obligation or direct interest to continue providing the service. From http://metamark.net/about#expire: Do Metamark links expire? The Metamark urls expire after five years or two years after the last usage - whichever comes later. However, if a link is never used, it will expire after two years. This should mean that as long as a link is on a public page, some search engine will visit it and keep it alive. Of course, this is subject to change and is no promise but just my intentions as of this writing. If you want guarantees you can make your own service. To be quite frank, I'm astonished the practice exists here in the first place. In my opinion it goes directly against the spirit of the Web envisioned by Tim Berners-Lee. A better practice would be to post long URL's within angled brackets. And there's no reason you can't do both, either. Which is why the archived summaries at deve.perl.org and perl.com all use the long form URLs. The metamarked URLs only ever appear as a convenience for readers on the mailing list. I am not about to start polluting my mailed summaries with such monstrosities as http://groups.google.com/[EMAIL PROTECTED] any time soon. You're welcome to write your own summaries that do use the full URLs of course. Or, if it bothers you that much, write something to run from cron once a month or so that grabs shortened summary URLs and does a simple GET on them. -- Piers Cawley [EMAIL PROTECTED] http://www.bofh.org.uk/
Re: loadlib and libraries with '.' in the name
On Mon, Sep 26, 2005 at 02:12:49PM +0100, Piers Cawley wrote: Joshua Juran [EMAIL PROTECTED] writes: On Sep 23, 2005, at 3:47 AM, Leopold Toetsch wrote: http://groups.google.com/[EMAIL PROTECTED] any time soon. You're welcome to write your own summaries that do use the full URLs of course. Or, if it bothers you that much, write something to run from cron once a month or so that grabs shortened summary URLs and does a simple GET on them. Then again who knows how long google group links will be good for. A summary is only a summary. It doesn't need to be good for ever. That is what rt/design docs/people are for. -- Piers Cawley [EMAIL PROTECTED] http://www.bofh.org.uk/ -- It is our job to proactively build progressive technology so that we may endeavor to authoritatively facilitate quality products while maintaining the highest standards
This week's summary
The Perl 6 Summary for the week ending 2005-09-25
Hello all. It's another Monday afternoon, which means I'm writing
another summary. There's no cricket to distract me this week, so I'm
letting iTunes Party Shuffle attempt to distract me instead.
This week in perl6-compiler
Nobody said anything on the list this week. I blame IRC.
Meanwhile, in perl6-internals
About multithreading
Leo pointed everyone at an article about about 'A Fundamental Turn
Toward Concurrency in Software'. Jonathan Worthington liked it.
http://xrl.us/hq4w
Bug Wrangling
It's possibly a failing of mine as a summary writer, but I've not been
following Parrot's RT traffic. Luckily, Joshua Hoblitt has volunteered
as a Bug Wrangler and he's hoping to increase the signal/noise ratio. To
that end, he'll be pinging people who reported bugs that are older than
3 or 4 months to find out if they're still current or can be closed. It
sounds like a mammoth task in the short term, but it also sounds like a
very useful project that'll get easier once the big house cleaning has
been done.
He hinted that this is the sort of project that *really* benefits from
having more than one volunteer doing the work.
Later in the week, he posted a bunch of IMCC TODOs.
http://xrl.us/hq4x
Tcl, exceptions in leo-ctx5
Andy Dougherty posted some more details about a bug in ParTcl when
running under Leo's branch. The bug seems to depend on whether there's a
slash in the script path passed to ParTcl. There was no response, but
hopefully work continues on fixing it.
http://xrl.us/hq4y
[RFC] Debug Segment, HLL Debug segment and Source Segment
Jonathan Worthington posted a discussion of how debugging segments could
work in Parrot in the future. He outlined a suggested unified debug
segment format that should work for both PASM/PIR and high level
language debugging requirements.
Roger Browne applauded Jonathan's efforts and made some further
suggestions.
And then the thread got Warnocked.
http://xrl.us/hq4z
Magic is useless unless verifiable
Jonathan Worthington posted a discussion about how Parrot bytecode files
should handle their magic number. At present, apparently, Parrot checks
the magic number only after it's tried to work out word size and
bytecode. Which is somewhat bass ackward. After some discussion, Chip
reckoned that the solution would be to have a magic string rather than a
magic number.
http://xrl.us/hq42
loadlib and libraries with '.' in the name
Ross McFarland found a problem with loadlib. Apparently it won't let
you load a library that has a '.' in the name. It turns out that fixing
things robustly isn't quite as straightforward as it at first appears.
Discussion ensued.
Ross posted a patch to RT.
http://xrl.us/hq43
http://xrl.us/hq44
Find copied and pasted code
That gentleman of great intelligence, sagacity, wit and annoying
capitalization; the one and only chromatic wondered what running PMD's
copy and paste detector plugin on Parrot's .c files would show. If
anyone has run it yet, they haven't reported on its findings, but it
surely won't be long now.
http://pmd.sf.net/cpd.html
http://xrl.us/hq45
Amber's Ashes Announced
Roger Browne announced the release of Amber for Parrot version 0.2.3a
(Ashes). According to the announcement, Amber's a Eiffel like scripting
language for Parrot. Joe Bob says Check it out!
http://xamber.org/index.html
http://xrl.us/hq46
Meanwhile, in perl6-language
\(...)
Oh look, a thread in p6l that's still going more than a fortnight later.
How unusual. This particular instance of the form is nominally about the
behaviour of \($a, $b) but various subthreads have drifted onto
discussions of context in general and meaningful whitespace. So far
there has been no discussion of the return value of
Pin.head.contents.grep - Angel $a {$a.is_dancing} but I'm sure it's
only a matter of time.
http://xrl.us/hq47
Junctions, patterns and fmap again
Luke continued to discuss Junctions and fmap with Stuart Cook.
http://xrl.us/hq48
Conditional wrapper blocks
Yuval Kogman discussed the inelegance of code that reads like:
if $condition { pre }
unconditional midsection;
if $condition { post }
And proposed a possible syntax that could be implemented in a macro. I
confess that I would be taking this thread more seriously if, when I was
writing this summary I had been able to come up with a realistic example
of code that had this problem.
Anyhoo, it sparked a good deal of discussion.
http://xrl.us/hq49
Object Model Pictures
Stevan Little's ongoing development of the Perl 6 MetaModel continues to
yield pictures. This week he incorporated Roles into the bigger picture.
Re: [PROPOSED PATCH lib/Parrot/Vtable.pm] Generate src/extends.c
On Sep 19, 2005, at 20:26, chromatic wrote: vtable_extend.patch Well, besides a nitpick regarding: +=item Cvtbl_extend($vtable) + + [ snipped ] + +sub vtbl_embed ... I'm fine with that patch. But the ultimate word should speak actual users of Parrot extend/embed, and of course, if it should be included in the upcoming release. leo
Re: ParrotIO crash
Joshua Hoblitt via RT writes: Should this become a TODO item? This code no longer crashes. Yes, make it a TODO that this should probably throw an exception.
Re: This week's summary
On Mon, Sep 26, 2005 at 18:12:23 +0100, The Perl 6 Summarizer wrote: Allomopherencing Not satisfied with inventing Exceptuations, Yuval invented Allomopherencing as well. Just don't ask me what it means because I don't know. It was just a bad joke on Exceptuation's expense ;-) The thread asks whether disabling strong and compile-time-angry type ineferencing should ever be disabled, since we have much better allomorphism-oriented support for typing and introspection. -- () Yuval Kogman [EMAIL PROTECTED] 0xEBD27418 perl hacker /\ kung foo master: /me spreads pj3Ar using 0wnage: neeyah!!! pgp1OJAfuThO2.pgp Description: PGP signature
