Now that intermission is over (yay!), I've got a pretty nice plan to Capturize Pugs (i.e. support the new Signature/Capture calling convention).
However, before we break all the internals into pieces, it'd be nice to push a point release out first, as the previous release was already three months ago. (Yes, grumpY!, I do hear you. :-))
The smoke status is already at a pretty good state; I've fixed a dozen or so of bugs, and implemented several trivial features (e.g. $+PATH and $ENV::PATH).
fglock++ and scw++ are exercising Pugs::Compiler::Rule's new :ratchet support, so the Perl5 rules runtime can also benefit from the 10x+ speedup brought by elimination of backtracking.
spinclad++ checked in Judy to third-party/. then hacked on its API docs to document the newly proposed key-iterating APIs. Once this API is in place, it'd be interesting to compare it with Perl 5's native hash algorithm...
Pugs now supports Unicode rules, thanks to pmichaud++'s hit on getting UTF8 data shuffled from/to PGE. pmichaud++ and TimToady++ also fixed some broken/outdated rules tests.
gaal++ is working on a Compilation Unit data type (CompUnit), to support an important feature of Perl 6, the doctrine of separate compilation:
use Foo;
use Bar;
In Perl 5, Foo can affect the way Bar is parsed, by introducing symbols to Bar, adding new global functions, or even by calling "require Bar" itself. However, in Perl 6 each module is compiled separately from a clean state, and Bar's compilation can only be affected by modules used from within Bar.pm itself.
Separate compilation cures many subtle action-at-a-distance issues, at the (very reasonable) cost of making things like Acme::use::strict::with::pride a bit more difficult to write, so I think it's a win overall. :-
Recent Comments