comment on

I skimmed this book over the weekend (thank you for the PDF download). There's an incredible amount of work in this book, and I appreciate that.

However, having said that, I suffer when I read this book in the same way I suffer when I read MJD's "Higher Order Programming". They both seem to require a bit more computer science background than I have (or have patience for). I'm a street-trained programmer, and have never set foot in a CS classroom.

In other words, my head hurt while reading this book, but that's not your fault. :)

-- Randal L. Schwartz, Perl hacker

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

In reply to Re: New Book: Exploring Programming Language Architecture in Perl by merlyn
in thread New Book: Exploring Programming Language Architecture in Perl by billh

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.


Keep It Simple, Stupid
	PerlMonks