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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Perl 6 and parrot outsider observations @YAPC::NA 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'd like to illustrate the v6.pm view with this v6-alpha CPAN stack [blogs.com].

    It is true that Perl 6's syntax is evolving and not for production. However, Perl 6's semantics is much more stable, and most of it has been feature-frozen for many months now.

    ...and that's why we can implement the semantics as pure Perl 5 modules, such as Moose [cpan.org], that involes no precompilation, and that you can use just like regular CPAN modules.

    And it's okay for only the underlying layers be production-quality for a while. People who'd like to help out with the surface syntax can hack on with "use v6-alpha" and integrate seamlessly into existing Perl 5 code; people who are just after some of the nice Perl 6 semantics can use the CPAN modules separately, without the need to switch syntax.

    • Audrey,

      Your comment has illustrated more clearly and concisely to me the direction perl 6 is heading. (Perhaps I should have attended one of your talks on the subject.) I've started digging into Moose and Class::MOP, and so far I like what I see. I'll have to look at some of the other items you list in your "Semantics" layer for more insight. More importantly, it now appears to me (much more than it ever has before) that there is both continuity and a clearer path to migration than I realized heretofo
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.