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.
  • Also, I wanted to respond to your point about how much time and research it takes to become a Perl expert. I agree--that's what it takes.

    It probably takes that for C, as well, although I wouldn't know since my C experience is somewhat limited (although I can read C and could pull something off in it if required, and have done a few small projects in it).

    However, that's actually one of my primary objections to Perl--that it takes so much. You could say, "Every language takes that long!" But I don't think it
    • But working toward Python best practices takes far less effort, I'd say, than equivalent Perl best practices, partly because the Python standard libraries are more extensive.

      I'm not entirely sure that that's true, nor even that that's the most important reason, but I do think you've reached a truth.

      Some of the defaults in Perl 5 are wrong. Some of them (particularly in the area of OO) are wrong in the sense that they don't work (SUPER:: is particularly broken for all but the simplest uses). Others a