Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

autrijus (1505)

  (email not shown publicly)

Journal of autrijus (1505)

Friday July 08, 2005
09:31 AM

Day 155: Polymorphic Existential Recursive Lambdas.

[ #25587 ]
As I'm going through my hackathon notes today, I remembered this new backronym for "Perl" I coined; lwall said he likes it, and for me it does summarize some of Perl 6's unifying designs that set it apart.

I really wish I can get out from this caffeine withdrawal and resume my daily summary of Pugs developments, as much exciting is happening, including a new DateTime::Set library that handles spans and recurrences, further solidified metamodel code and the beginning of S12.5: Metamodel. Dialogs such as this on #perl6 amuses me:

<robkinyon> heyla, nothingmuch
<robkinyon> stevan told me about your crazy P6 plans
<nothingmuch> which crazy plans? I have several =)
<robkinyon> aren't you involved in the PIL -> P5 effort?
<nothingmuch> yep, sort of
<nothingmuch> i'm thinking in a diff direction now, and not writing code at the moment
<robkinyon> wow, a hacker who stops and thinks
<robkinyon> next, you're going to tell me that you're writing down a design or something!

Allison resumed journaling today, this time talking about the relationship between TPF and Pugs. I'm very happy to see the Perl 6 process getting more visibility; leo's journal is really helpful, and I heard that luqui will help to push cabal meeting minutes to the public, similar to how Mozilla Staff Meeting Minutes is handled. All in all, great news.

Parrot's exposure seems to picking up momentum, too: the 0.2.2 release is reported in lambda the ultimate; today John Lenz announced on p6i that Chicken Scheme starts to target Parrot.

That's it for today. See you tomorrow!

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.