On Mar 18, 7:22=A0am, stephen...@[EMAIL PROTECTED]
(Stephen Pelc) wrote:
>
> MPE uses literate programming of a sort for all our code. While I
> agree that specs for applications are rare these days, the comments
> for a word can easily be the specification for that word. Our
> experience is that writing the spec for a word first reduces bugs
> and improves maintenance costs and time.
>
Literate programming has some advantages, like keeping the
do***entation more in sync with the code and simplifying sup****t for
multiple do***entation formats (HTML, PDF, XML, etc.).
Recently I've taken to writing about the design of the code (in Open
Office) while coding, switching back and forth between activities. In
OO Writer (or Word etc.), I'm designing top-down. In the text editor I
use for Forth, I'm implementing bottom-up. I find it more appealing
than mixing top-down and bottom-up styles in the same do***ent. Mostly
I don't like cluttering the code with commentary that belongs in
manuals.
Brad
|
