From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 109fba,b87849933931bc93 X-Google-Attributes: gid109fba,public X-Google-Thread: fac41,b87849933931bc93 X-Google-Attributes: gidfac41,public X-Google-Thread: f43e6,b87849933931bc93 X-Google-Attributes: gidf43e6,public X-Google-Thread: 103376,b87849933931bc93 X-Google-Attributes: gid103376,public X-Google-Thread: 1108a1,b87849933931bc93 X-Google-Attributes: gid1108a1,public X-Google-Thread: 114809,b87849933931bc93 X-Google-Attributes: gid114809,public From: Ian Joyner Subject: Re: What is wrong with OO ? Date: 1996/12/31 Message-ID: <32C8521C.800@acm.org>#1/1 X-Deja-AN: 206842262 references: <32A4659D.347A@shef.ac.uk> <32B81DA7.6D08@deep.net> <59vr2s$55r@masters0.InterNex.Net> <5a0niaINNlda@topdog.cs.umbc.edu> <5a29dv$hb2@masters0.InterNex.Net> <32c7725d.3390649095@news.zip.com.au> content-type: text/plain; charset=us-ascii organization: Unisys mime-version: 1.0 reply-to: i.joyner@acm.org newsgroups: comp.lang.c++,comp.lang.smalltalk,comp.lang.eiffel,comp.lang.ada,comp.object,comp.software-eng x-mailer: Mozilla 3.0Gold (WinNT; I) Date: 1996-12-31T00:00:00+00:00 List-Id: John (Max) Skaller wrote: > > On 28 Dec 1996 04:58:39 GMT, clovis@wartech.com wrote: > > >Would someone PLEASE and QUICKLY hang those who insist that code is > >"self-documenting?" > > The code I write _IS_ self-documenting. > But then, I do write using a literate-programming system :-) I think code should be written to be self-documenting, but certainly it is not self-documenting in itself, unless you have a conscientious programmer like John. But yes it can and should be self-documenting. Since we are talking about documentation, how many documents should you produce on a project? Many people I suspect would start to enumerate 'requirements spec', 'functional design doc,' 'detailed design', etc. However, the answer, I think is one! Only one document should be produced for any project no matter how large. This will link requirements and functions with bits of program, etc. With facilities like OpenDoc and to a lesser extent OLE becoming available, such documents will be possible. But they will require better programming languages. What made me think of this was that Bill Gates stated in his book that Boeng designed the entire 777 aircraft using one gigantic electronic document! Physical engineering disciplines have made good use of computing technology, it's about time software engineers followed the same path... better and more productive languages and environments, and stop defending archaic 25 year old languages from another era. And this gets back to a point Robert Martin made quite a while ago in this thread, that analysis and design is programming, and that these should not be done by different groups. For more thoughts: http://www.progsoc.uts.edu.au/~geldridg/cpp/cppcv3.html ------------------------------------------------------------------------ Ian Joyner | "for when lenity and cruelty play | All opinions are Internet email: | for a kingdom, the gentler | personal and are i.joyner@acm.org | gamester is the soonest winner" | not Unisys | William Shakespeare Henry V | official comment ------------------------------------------------------------------------