Stories
Slash Boxes
Comments
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)

autrijus
  (email not shown publicly)
http://pugs.blogs.com/

Journal of autrijus (1505)

Monday October 31, 2005
05:20 PM

Day 241: Third day at Liz's - Sketch, PA02, Param syntax

[ #27397 ]
#parrotsketch meeting last night was a success:
  • leo++ for finishing the variable-sized register frames
  • pmichaud++ for getting shift/reduce parser to parse rules itself
  • allison++ for announcing the availability of tree transformations (aka Attribute Grammar) and linking to compiler tools document. I love the upfront declaration of Rule number one: writing compilers is not hard., but would like to amend it with ...with the right tools. Read the comptools documents for the set of Right Tools coming to Parrot.

Liz and I keep finding serializable continuations very useful for S17, especially for intospection and development purposes (imagine "stepping back" in your debugger). It seems that the next JVM release may support Rhino-style serializable continuation, which would make it a first-class perl6 target.

Lots of nice feedback on S17. Still need to tackle coro, junctions and hyperops in the face of multiple core CPUs.

Stevan started populating Perl6-ObjectSpace with Real Code (tm).

iblech fixed Pugs parser and internals to deal with the syntax change in the new S06. The commit log provides a succint summary.

Looking forward to tomorrow's Amsterdam.pm meeting.

Note to self: fix the bug reported by xinming: class a { has $.a; method update { $.a; } };class b { has $.a; submethod BUILD { a.new( a => $.a ).update; }; }; b.new( a => 20 );

Wendy and I started annotating the illustrations with simple question/answer notes, captured in the rough sketch that will hopefully become an accessible PA02: Architecture. Pugs has long suffered from the steep initial learning curve; the Apocrypha series was planned to remedy that, but somehow I lost the perspective of explaining things in a concise fashion. To that end, the ObjSpace coding was delayed for a day, but I think it's worthwhile to apply the same Q/A treatment for PIL, Object Space, MetaModel and the rest of Pugs jargons. Feedback welcome!

Now I'm off to Amsterdam.pm meeting, which means lots of communication and less coding for today. Wish me luck!

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