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.
  • You're definitely right about the whole sharp tools vs professional stuff.

    I wouldn't mind seeing a danger-factor or something for the features discussed.

    There's a lot of stuff that is in the sharp categories I only find I need once every few years (flip flop conditionals, the @- and \G stuff, and so on).

    They are badly needed when you need them, but you need them SO rarely.
    • Or goto. :-)

    • Flip flops! Damn it, I didn't put that in the book. I knew I was missing something. :)

      I've have to think about how to mark some things with a big caution sign. O'Reilly has marginal glyphs for that sort of thing. That means that I'll have to go back through the book and figure out which things are too pointy.
      • Yeah, I was surprised that flip-flops weren't in there... once Adam mentioned them. I use them very rarely, but it's always "hilarious" when I look at six or seven lines of code and realize, "Hey, that's a one-liner with ..."

        The only other two omissions that I thought were notable were in the error handling chapter. I was surprised you didn't mention Exception::Class, but that's largely because I use it so extensively. I was much more surprised that you didn't mention SIG{__DIE__} at all.
        --
        rjbs
  • I should add somthing about $&'s performance issues. That one probably got away because we talked about it in Learning Perl so I figured that we had a footnote on it's downside. Now that I look at Learning Perl, though, I see that we don't and it's just something I talk about in classes.
    • When I wrote my review and looked back on chapter two to make sure my notes weren't wrong, it occurred to me that it would be pretty simple and apropos to stick in just one or two sentences like, "Unfortunately, using $& once can slow down your whole program. Fortunately, you can work around it with substr, @- and @+. You can use those for more more, though, like..."

      To get back to the "stuff a pro knows," I like to think that before using any punctuation variable, a real pro first reads the perlvar do
      --
      rjbs
  • I'm not up on the different ways O'Reilly does Safari, but I recall a part of it where you could put together a library based on select chapters of books. If you don't want the point weapons parts of the Vicunas (them's those animals), you could select the chapters you like and fail to mention that the others exist. :)
    • <@rjbs> Read this book before you write any code.
      <grasshopper> Ok... why are the chapter numbers out of order and missing sections?
      <@rjbs> It's a riddle.  See if you can find the next number in the sequence.
      --
      rjbs