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.

Dynamic languages 6 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Not strictly related, but: "Ruby 1.8.6 and Python 2.5 are both first-class languages for Mac development [apple.com]".
    • Why? I'll tell you why.

      Because Perl is resistant to being processed by development tools.

      Plain and simple.

      This is the same reason that Google goes for Java and Python mainly, because you can write huge toolchains around it.

      Perl is impossible to parse.

      • Perl is impossible to parse.
        No longer so. Take a look at PPI [cpan.org], which is a programmatic way to parse and manipulate Perl code without perl. But I agree it probably came too late (2002? 2003?).

        • Take a look at PPI [cpan.org]

          You know you are talking to the author of PPI, right?

        • PPI is a programmatic way to parse and manipulate Perl documents.

          It is NOT a way to parse and manipulate Perl code.

          I know you probably didn't mean to say it in those terms, but the distinction between code and document is extremely important in this case.

          This is why providing method name tab-complete, probably the most obvious of all editor assistance functions, is incredibly difficult to do in Perl.

          Even after PPI came out, it took a long time for people to realise that "syntax parser" was not necesarily go
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.