Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Schwern used to have a great checklist online called the Perl Book Litmus Test. While rather unscientific, it was an easily taught test which manages to catch a frightening fraction of bad books. Since the site he had it on is now dead, hopefully he won't object to my posting it here. Just open the index and answer the following questions:
  • localtime Does it state that it returns the number of years since 1900? Does it mention that when used in scalar context it returns a nicely formated date?
  • srand Check how it uses srand(). Does it warn you to call it only once in a given program? (If srand is never mentioned, that's okay)
  • Number of elements in an array Does it say that an array will return its number of elements in scalar context, or does it use $num = $#array + 1;
  • flock Does it discuss and use flock instead of lockfiles? (ie. setting some .lock file instead of using flock()) Its okay if file locking is never discussed at all.
Grab a Perl book and try it. Wasn't that easy? It is a useful test, but too easy. It is perfectly possible to pass this test but still suck. However most bad books will fail it.

For a more involved discussion on how to tell good from bad I would recommend reading Choosing a Perl Book by Simon Cozens.


In reply to Re (tilly) 1: Reviewing bad books. by tilly
in thread Reviewing bad books. by gmax

Title:
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?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others having an uproarious good time at the Monastery: (4)
As of 2024-04-23 06:11 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found