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.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no 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-15 07:15:18 PST Path: archiver1.sj.google.com!newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!isdnet!psinet-france!psiuk-f4!psiuk-p4!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: powerful editors versus IDEs (was: License to Steal) Date: Tue, 15 May 2001 10:02:08 -0400 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: <9drct2$gpq$1@nh.pace.co.uk> References: NNTP-Posting-Host: 136.170.200.133 X-Trace: nh.pace.co.uk 989935330 17210 136.170.200.133 (15 May 2001 14:02:10 GMT) X-Complaints-To: newsmaster@pace.co.uk NNTP-Posting-Date: 15 May 2001 14:02:10 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.sj.google.com comp.lang.ada:7518 Date: 2001-05-15T14:02:10+00:00 List-Id: In a perfect world, Configuration Management and Change Control would be integrated in such a way that the change history for a given module is not maintained as comments in the module, but as an attachment of some form that you can retrieve as needed. A good CM system I've both developed on and used, had change requests associated with the check-out/in process. If you had questions about what changes had been made to a module, you could always find the collection of change requests that have ever impacted it and could retrieve older versions of the module to compare against. That way the code (or any other artifact within the CM system) had no clutter that wasn't relevant to its current purpose, but you could find out how it had evolved if it was necessary to do so. At *most* you might see someone having put a comment in the banner of a module that referenced a CR# - but I never believed any of that anyway because it was not always up to date. It was far better to ask the computer to fill you in on the module history. MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com Web: http://www.mcondic.com/ "Beard, Frank" wrote in message news:mailman.989885292.1844.comp.lang.ada@ada.eu.org... > > While that sounds perfectly reasonable and better than our current > approach, we are never allowed to go back and do that. We have to > have a justification for checking the unit out, updating it, and > checking it back in. To clean up the code is not sufficient. So, > some poor guy down the road will have to maintain it with the noise > in place. > > I would rather not put it there in the first place. >