in reply to Re^3: An Introduction to Literate Programming with perlWEB
in thread An Introduction to Literate Programming with perlWEB

The drawing isn't the document; it's a part of the document, like Chapter XIV in Moby Dick. Maybe the difference is largely nomenclature, in that you're viewing the drawing as a product, analogously to a computer program, where I don't: it's a step, used to describe a part's geometry and no more a complete part description than "steel." On a drawing, one wouldn't say "bolt" without quite a lot of further information, like the size.

From here on was added in an update.

Oddly, I agree with many of your issues with LP, in that it adds a pre-processing layer, and even adds the complication of re-ordering code. I tend to view it as a very elaborate scheme of commentary, which may be a complete misinterpretation of its goals.

Information about American English usage here and here. Floating point issues? Please read this before posting. — emc

  • Comment on Re^4: An Introduction to Literate Programming with perlWEB

Replies are listed 'Best First'.
Re^5: An Introduction to Literate Programming with perlWEB
by BrowserUk (Patriarch) on Jan 13, 2009 at 19:09 UTC
    you're viewing the drawing as a product, analogously to a computer program, where I don't:

    As a one-time indentured draughtsman and qualified Mech.Eng, I can tell you that your interpretation is discordant with the way engineers view blueprints. Each blueprint has its own document no.; modifications history; title; keys; etc. They are "documents" in their own right. And in combination with materials lists--which sometimes are included on the drawings, they can be a complete specification for the manufacture of the product.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Meditations