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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fac41,af40e09e753872c X-Google-Attributes: gidfac41,public X-Google-Thread: 109fba,f292779560fb8442 X-Google-Attributes: gid109fba,public X-Google-Thread: f8c65,30e368bdb3310fe5 X-Google-Attributes: gidf8c65,public X-Google-Thread: 1014db,30e368bdb3310fe5 X-Google-Attributes: gid1014db,public X-Google-Thread: 1008e3,30e368bdb3310fe5 X-Google-Attributes: gid1008e3,public X-Google-Thread: 10db24,30e368bdb3310fe5 X-Google-Attributes: gid10db24,public X-Google-Thread: 103376,30e368bdb3310fe5 X-Google-Attributes: gid103376,public From: ok@goanna.cs.rmit.EDU.AU (Richard A. O'Keefe) Subject: Re: Hungarian notation Date: 1996/06/06 Message-ID: <4p5sk6$hcq@goanna.cs.rmit.EDU.AU>#1/1 X-Deja-AN: 158734981 references: <31999F43.41C67EA6@scn.de> <4ns02o$ep3@goanna.cs.rmit.EDU.AU> <4o07o9$rfu@seagoon.newcastle.edu.au> <4o4jeg$7e6@tpd.dsccc.com> <4p49vq$etm@nntp.seflin.lib.fl.us> organization: Comp Sci, RMIT, Melbourne, Australia newsgroups: comp.lang.ada,comp.lang.c++,comp.lang.c,comp.lang.modula3,comp.lang.modula2,comp.edu,comp.lang.eiffel nntp-posting-user: ok Date: 1996-06-06T00:00:00+00:00 List-Id: z007400b@bcfreenet.seflin.lib.fl.us (Ralph Silverman) writes: >*********begin r.s. response************* > the idea, > that > comments should > outlive and outlast > original code > when that code has been modified... > is extremely horrifying and bizarre! > however, > this does raise an intersting question... > version control for comments! The indentation, of r.s. is unusual and unhelpful. (:-) What is bizarre about the notion? I often have big comments explaining the purpose, assumptions, and interface of a module. These comments almost always survive major changes to the implementation. They are in the source file for two reasons: (a) so that I can read them while I'm working on the module and am reminded of what I'm supposed to be doing (b) so that if some change _does_ invalidate a comment, the comment is there handy for me to revise. I don't see any special problem for version control. *All* documents used in the construction of a software system are kept under version control, ideally under configuration management. -- Fifty years of programming language research, and we end up with C++ ??? Richard A. O'Keefe; http://www.cs.rmit.edu.au/~ok; RMIT Comp.Sci.