in reply to what does 1; does?

Books about Perl (and most other "technologies") are mostly a waste of money. Perl itself comes with excellent documentation and many examples, as do most widely-used modules. People on Perlmonks are usually quick to answer questions not found in these docs.

Replies are listed 'Best First'.
Re^2: what does 1; does?
by chromatic (Archbishop) on May 05, 2008 at 16:59 UTC

    Oh, I can think of several books which cover things most definitely not found in the documentation....

[reply]
      True. For example, the Ruby/Rails guys figured this out and wrote a language and framework with completely shoddy documentation, thus creating a wonderful book market. Luckily, Perl hasn't followed this path.
[reply]

        To be fair, the reason Ruby had such lousy English documentation is that it originated in Japan.

        There's no excuse for the state of the core Rails documentation, however.

[reply]
Re^2: what does 1; does?
by CountZero (Bishop) on May 05, 2008 at 16:19 UTC
    All too true!

    But nothing beats having the Camel book on your desk, if nothing else it identifies you as an "old hand" in programming (so does having the COBOL and FORTRAN programming manuals lying around, although you have to lock these up in safe storage when you are away as they have antiquarian value now).

    CountZero

    A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

[reply]

In Section Seekers of Perl Wisdom