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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,629e11b80bdec45d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-05-13 22:55:28 PST Path: archiver1.sj.google.com!newsfeed.google.com!newsfeed.stanford.edu!newsfeed1.bredband.com!bredband!newsfeed1.telenordia.se!algonet!newsfeed1.funet.fi!newsfeeds.funet.fi!nntp.inet.fi!central.inet.fi!inet.fi!read2.inet.fi.POSTED!not-for-mail From: "Anders Wirzenius" Newsgroups: comp.lang.ada References: Subject: Re: powerful editors versus IDEs (was: License to Steal) X-Newsreader: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Message-ID: Date: Mon, 14 May 2001 05:55:26 GMT NNTP-Posting-Host: 194.251.142.2 X-Trace: read2.inet.fi 989819726 194.251.142.2 (Mon, 14 May 2001 08:55:26 EET DST) NNTP-Posting-Date: Mon, 14 May 2001 08:55:26 EET DST Organization: Sonera corp Internet services Xref: archiver1.sj.google.com comp.lang.ada:7474 Date: 2001-05-14T05:55:26+00:00 List-Id: Simon Wright wrote in message ... >"Beard, Frank" writes: > >> I miss the repeat function in emacs, where you could repeat >> an action anywhere in a file. That would definitely come in >> handy when we have to add an update comment to the end of >> every line that we modify. > >Jings! management gone mad! you need to look into a proper source code >management system. CVS is free (so is SCCS, but why you would want to >use it I don't know ..) > >What do your source files look like after a few updates? full of crap >telling me who changed stuff and (perhaps) why, completely obscuring >the program logic and making it look so ugly that anyone with the >faintest sense of aesthetics comes over faint when asked to look at >it. A method I used to practise in a former programmer life was to add comments at the end of each updated line. When the current updating task was done, tested and released, the line end comments where removed and replaced by a short description in the header of the module. With that method we didn't have to bother what comments to write in the header each time we changed something. The summary was easy to write by reading through the line end comments. Anders Wirzenius