One of the reasons O'Reilly books can't charme is are the poor indices . . .

Perhap. I'm comparing the Camel's index with the multitude of "Learning Perl for Fools" books out there, where they basically slap an index with a few common terms and leave the rest to the poor sod that bought the book.

What I also don't understand is that you wouldn't buy certain classes of books, because they are easily outdated, yet you break a lance for the Camel.

How much fundamental of the Camel was really obsoleted by 5.6.* or 5.8.*? Declaring variables is still the same. Looping and conditionals are the same. Declaring subroutines is the same, with at best a few attributes being added, if anything. Builtins are pretty much the same, with a few details being different. Complex datastructures, packages/modules, and OO programming are the same (notwithstanding meryln's complaints about ref $class || $class;, or the various other object systems you can use under Perl). Trying to output native, optimized code from your Perl code is still a tricky proposition. Tied filehandles became useable in 5.6.0 (IIRC), but that's a fairly small portion of the book, and it covers them anyway. Threading became somewhat useable in 5.8.0, but again, it's a small part of the book.

So small, specific sections might be a bit out of date, but I don't forsee it being unuseable at least until Perl6. That's a long ways off and a lot of Perl5 stuff will still be applicable by then. Probably Perl4, too.

----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer

Note: All code is untested, unless otherwise stated

In reply to Re: Re: (OT) I prefer to do my learning with: dead trees or flying electrons? by hardburn
in thread (OT) I prefer to do my learning with: dead trees or flying electrons? by revdiablo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.