Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

PBP is a very good book. It gets actually better at each read. One thing touched only on the surface is logging (at least in the sense that it does not advise much about existing logging modules)

  • is log4X actually good for production?
  • should one prefers syslog type logging
  • etc...

    one thing I liked pretty much (and that can be said for perlhacks too) is that in the first reading (along the diagonal) you can ignore the bits you find a bit boring and browse the index for your favourite sections (some smelled real good just by the title ;)

    Inside-out OO is maybe rushed a bit. I mean the arguments are sound and I knew the technique (eh eh from here++ actually) but I felt a bit "pushed" to embrace it...after all there is a huge codebase where almost everybody has invented its own object system, so a bit more of a pacific coexistence (or survival) howto would have been good.

    still I buy a lot of books (and 80% are o'reilly books, enough to be given a prize some day :)) and PBP has been (is) my best read in months -- I must confess that on my bedtable (yeah it did not leave it yet!) it is sitting next to Pierce's Types theory and Queinnec's Lisp in little bits (and looks all the sexier...).

    hth --stephan

    In reply to Re: Best Perl Practices reviews? by sgt
    in thread Best Perl Practices reviews? by Anonymous Monk

    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.
    Log In?

    What's my password?
    Create A New User
    Domain Nodelet?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others making s'mores by the fire in the courtyard of the Monastery: (2)
    As of 2023-01-29 09:34 GMT
    Find Nodes?
      Voting Booth?

      No recent polls found