Much like
Juerd said, Learning Perl is good but will get stale fast for someone with a programming background. Don't get me wrong, I like the book and all, but working through all of it seems like it's burning otherwise useful time.
Teaching
perldoc is good, I'd also recommend reading
perlman:perltrap (at least the first part, I'm sure some parts of the C traps carry from Java well), which I found useful as a CS student transitioning from C/C++/TCL to Perl. Heck, my first question here was answered in
perltrap.
If you've got some money, I'd actually recommend picking up the Perl CD Bookshelf 2.0 from O'reilly - it comes with Perl in a Nutshell in deadtree copy, and five books on CD that are handy to search through and whatnot. The first Perl CD Bookshelf had six books, and I don't recall what was eliminated, but CD Bookshelf 2.0 has Programming Perl, Perl in a Nutshell, and the Perl Cookbook, which is excellent to get some understanding from.
~Brian
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.