Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Do your authors not know The Elements Of Style? Maybe it should be a contract signing bonus: The O'Reilly Imprint of Strunk & White.
    --

    --
    xoa

    • Actually, we talked for a while about putting together a care package of Don't Write Like The President Speaks books, but eventually decided it'd be cheaper and easier in the long run to just have people write sample chapters first :-)

      --Nat

      • Don't Write Like The President Speaks books

        In fairness, though I love the President, I laughed out loud at that thought. :)

        --
        J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • I really like the idea about a Technical Writing and Grammer RFC [ietf.org].

      I wish I had sufficient round tuits to turn Strunk and White into a proper RFC, complete with MUST, SHOULD, MAY, etc. Does anybody here have RFC experience and want to give it a go?...

      --

      -DA [coder.com]

      • Do not spend time writing an RFC. They already exist as The Chicago Manual of Style, The AP Style Book, The Economist Style Guide, Strunk & White's Elements of Style, and so on. Creating another resource for writers who already do not use those is a waste of energy. You could hardly do better than those, and at best start an endless series of language flame wars.

        Besides that, each publication has their own rules and style. No one style is the correct style. The first principle is Consistency, and