home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!hpscit.sc.hp.com!scd.hp.com!hpscdm!hpuerca.atl.hp.com!sailer
- From: sailer@hpuerca.atl.hp.com (Lee Sailer)
- Subject: Re: Criticisms Wanted
- Message-ID: <BxznBF.ELu@hpuerca.atl.hp.com>
- Date: Fri, 20 Nov 1992 00:14:02 GMT
- References: <1e1cccINNbsc@terminator.rs.itd.umich.edu>
- Organization: Hewlett-Packard NARC Atlanta
- X-Newsreader: Tin 1.1.3 PL5
- Lines: 24
-
- Paul Potts (potts@oit.itd.umich.edu) wrote:
- : In article <1992Nov13.060823.1358@BofA.com> dan@BofA.com (Dan Brockman) writes:
- : >In article <1992Nov11.175117.15325@bcrka451.bnr.ca> sjm@bcrki65.bnr.ca (Stuart MacMartin) writes:
- : >>
- : >Reading source code is hardly a crime. He could be trying to fix the damned
- : >bug his benighted colleague wrote into the program. He could be trying to
- : >find the damned bug.
- :
- : If I could get by without doing it, I would certainly prefer it. The
- : programmers that wrote some of the classes I'm using might have been
- : making a lot of money, but they sure don't know how to write readable
- : code. The biggest reasons seem to be:
- :
- )
-
- I like reading the source. But good documentation is very handy, too.
-
- perhaps a good compromise is "literate programming". In LP, the documentation
- and the code are the same thing. As implemented by web, filters exist
- which convert the well-documented code to user readable documentation. Other
- filters convert the same code into stuff the compiler can use.
-
- lee
-
-