Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • I always cringe and want to shout expletives when I see "PERL" and not "Perl".
  • I have been speechless for minutes, after reading this. This is a post I feel I should reply to, to express how I think about it. But it was too much of a shock. My thought and feelings about this book are extremely hard to describe.

    It's the same kind of feeling I get when I see someone without arms and legs, who is blind and deaf. I really do wonder how the author of this book manages to live with such a huge handicap. Not even the combination of great stupidity and even greater ignorance could stop him fr
  • Warning! Do not download and read the example code from the website! The misuse of HTML 2, let alone the abyssmal Perl code, will burn your eyes out.

    Oh, the horror! Ovid, I curse you for exposing me to this evil. I want my ignorant bliss back.

  • Ah. Deja-vu. This reminds me a lot of the time I spent doing detailed reviews of "Perl and CGI for the World Wide Web" and "CGI 101".

    I left a comment on the book's feedback page and I got a response from the author which pretty much missed all of the points you've made. I've send another, more detailed, reply. I'll let you know how it goes.
    • I received a reply, too. I'm rather disturbed at how blithely the author took the my commentary though I must say that I was happy the publisher took the report seriously enough to contact the author.

      • I emailed the publisher explaining that none of the best practices that have come about in the last ten years were included in the book, etc. I got the following paraphrased response from the author:

        I am surprised and impressed that a professional PERL programmer bought my book.

        My code examples produce the correct output for the environment I specified.

        Due to space restrictions I decided not to enhance the code examples to improve security, instead I kept them short for simplicity.


        • OK, that's very interesting. You see, that's the exact same response I received. I wonder if the publisher is lying?

          I'm sorry this reader was unhappy with my PERL book. I am flattered, and a little surprised, that a professional PERL programmer is buying this book. The listed code examples produce the illustrated output in the environment described. These could be enhanced to improve security but the additional code would extend beyond the space available. The examples are kept brief for simplicity. Tha

          • Yes, that's exactly what I received. From Harshad Kotecha.

            It might not be the publisher who's lying. It might be that the author has a canned response to any criticism brought to him from someone who knows what they're talking about.

            Who knows? The response to me looked genuine enough. It's definately shoddy work to send the same response to two different letters presumably bringing up somewhat different issues!