Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Though very promising and fun, i actually found this book quite lacking in certain areas. One example is the BTree description. The way a btree is described is actually the difference between a B+Tree and a regular one, thus causing confusion. Another example is the cryptographic section, where this actually a guide to using a module. I think this has a bit too much examples, not enough theory. Statements such as 'here is the code, but we're not going to discuss it' wreak of laziness, and i think i can spot a handful in the book.

The book is well written, but i think, at the bottom line, could have been more complete, better organized, and more mature. Perhaps a slightly more narrow spectrum would have aided. I would be reluctant to reccomend it until newer editions come out.

zz zZ Z Z #!perl

In reply to Re: Mastering Algorithms with Perl by nothingmuch
in thread Mastering Algorithms with Perl by splinky

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

  • 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.