[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Source code second thoughts...
- To: firstname.lastname@example.org
- Subject: Source code second thoughts...
- From: email@example.com
- Date: Fri, 31 Aug 90 09:09:55 BST
- In-reply-to: George Williams's message of Thu, 30 Aug 90 20:55:54 cdt <9008310155.AA19307@huntsai.boeing.com>
- Reply-to: Andrew Ormsby <firstname.lastname@example.org>
> Date: Thu, 30 Aug 90 20:55:54 cdt
> Realistically, the amount of documentation required for the source
> code would be EXTREME! Do we really want to impact the development
> of MACL by making the developers produce documents suitable for
Often it is useful to have the source code. But on the other hand, I
don't want to, and shouldn't have to search through huge amounts of
source code trying to figure out how something works. One of the
advantages of a good object-oriented design is supposed to be that you
should be able to hide how things work internally and document the
interfaces. After all, we don't want to be dependent on how things
work internally, or each time there is a minor change, our code will
What I'm really saying is that in an ideal world, yes, I DO expect
developers to supply complete and accurate documentation. This isn't
always a realistic proposition.
> George Williams
CS Dept., UCW Aberystwyth, Wales.