In general I prefer books (or printed manuals) because I find them easier to read, easier to jump from one place to the other, for making annotations, etc. I learned perl from the manual page, back when there was only one manual page, and although I did have a copy of the original Camel many years ago I don't have the book now. As Abigail noted, the important thing for me regarding perl is to know where to look for things when I need them (and I'll second the vote for Stevens'
Unix Network Programing!).
I have similar problems with the Sybase documentation - it stretches over 15 or so PDF files, some of which should really be read cover to cover, but reading a 600 page PDF file on a computer screen isn't the most pleasant thing to do, especially when you don't have a 20 year old's eyes anymore. I'd much prefer to have these manuals in paper format, but unfortunately that's not an option anymore. I suppose I could print them, but that would take a month on my little ink-jet :-)
Michael
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.