comment on

Cookbook provided higher value for me than Camel, perhaps mostly because of the way it's organized. But both are invaluable.

So can we make this a quartet, or -- better yet -- a quintet?

If so, Camel joins my list, along with either Perl Debugged or the Debugger Pocket Reference

Ooops. Sextet, anyone?

No, make that "septet" because I'm sure to think of another as soon as I post this.

Seriously, Perl is blessed with what seems to me an extraordinarily wide selection of excellent books (and, of course, a few that would have better served the world had the trees chopped down to make paper to print them had been left to grow.

Update (in response to the comments above re MRE): Regexen are but one tool among those that make TIMTOWTDI a watchword for Perl.. but they are a tool. The Perl coder without broad and deep knowledge of regexen is suffering a handicap on the same order as the proverbial fighter with one arm tied behind his back.

In reply to Re: So what is your Perl book "Trilogy" anyway? by ww
in thread So what is your Perl book "Trilogy" anyway? by ait

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks