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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • "Of course, you'll never actually have to write anything like that yourself, since the Perl 6 distribution will come with a fully generalized source code translator program."

    I wish Damian and others would stop saying that. Perl 6 itself is completely vapourware, so lets not build vapour on top of vapour, please. The Perl 5 translator module is the least appealing job of all the possible perl 6 tasks. So it's likely to get done last, if at all.
    • The Perl 5 translator module is the least appealing job of all the possible perl 6 tasks.

      Oh, I dunno. Writing the Perl 6 parser is going to be an incredibly unpleasant job for someone. (That's why I really wish people would stop claiming that the Perl 6 syntax is going to be "more regular". It's not. It's going to be harder to parse than Perl 5. Believe me, I've tried.)

      The translator shouldn't be that bad. If you can go from Perl 5 to Python [goebel-consult.de], I don't see going from Perl 5 to Perl 6 to be that difficult.

      Of course, it'll only be useful if someone ports all those XS modules that all our code depends on, but we can get to that in time...

      • The Perl 5 translator module is the least appealing job of all the possible perl 6 tasks.
        Oh, I dunno. Writing the Perl 6 parser is going to be an incredibly unpleasant job for someone.
        So I guess this is why we haven't seen any code written other than the core, huh? Sheesh. It's such a bummer. I was looking forward to a new perl.