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.
  • This helps ensure the evolution of Perl, as many programmers can experiment with creating new Perl features in a clean fashion...

    The cleanliness of their results depends on their skill. At least you know if your Perl 6 programs stop working, you have a grammar problem (whereas I have to work fairly hard to make a completely invalid Lisp program; maybe I'm bad at macros).

    • Grammar-level errors are one reason why I'm excited about Perl 6. I still have bad memories of maintaining C macros (and even a homegrown, standards-compliant C preprocessor). Getting your grammar errors at the grammar level, rather than debugging a macro that preprocesses and compiles fine but does not work, sounds like working at the Right Level to me.