Knowing that there's a large difference between 'consumer' computer magazines and peer-reviewed scientific journals, I'm surprised that there is no process by which the author gets a proof or pre-print of the article before it goes to press to correct any errors that may have come about from typesetting. Sure, this delays the printing process more, but I would think particularly with a mix of text and code, an author would want to check to make sure everything's ok. In addition, I've seen cases of final articles in computer mags where the graphic-arts people went overboard on the clip-art-and/or-graphic-effect of the month and made the article itself practically impossible to read.

Maybe this needs to be done; sure, the web version might be correct, but to most, the paper copy is going to have the most impact, and for code to be mangled that badly as to detract from the article could hurt the author's reputation despite the error not being his to start with.

-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain
It's not what you know, but knowing how to find it if you don't know that's important

In reply to No Proofs/Pre-prints? by Masem
in thread How to avoid being mangled in Print by dws

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.