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.
  • There very well could be a similar book for another language in the medium-term future. It may not include the railroad diagrams, however.

    • You don't think the railroad diagrams totally make the book or what?

      I actually just read that same quote the other night (because I skipped to "the bad parts" when I ran across some WTF parts having gotten somewhat bored with the explanation of the syntax parts.) But I have to disagree because I'm thinking that the worst part of the language is the lack of block scoping because it makes closures nearly useless without acrobatics (these acrobatics are the WTF part.)

      My suggested solution would be to just rem

      • Perl, Javascript, Ruby and Python share almost the exact same expressiveness, and in a pinch I wouldn’t be unhappy about having to work in any of those. The order in which I listed them is my order of preference – yes, I like Javascript better than Ruby.

        The absence of proper block scope is common to all of these languages except Perl, btw.

        (Note that Ruby 1.9 will fix block scoping – but only for closures, not in general, thereby adding to its already large pile of non-composable one-off features. Even Perl is more regular.)