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.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5894fe67040038b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-08 08:37:00 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!195.54.122.107!newsfeed1.bredband.com!bredband!newsfeed01.nntp.se.dataphone.net!nntp.se.dataphone.net!193.213.112.26.MISMATCH!newsfeed1.ulv.nextra.no!nextra.com!news1.oke.nextra.no.POSTED!not-for-mail Reply-To: "Frank" From: "Frank" Newsgroups: comp.lang.ada References: <9s9iti$g$1@nh.pace.co.uk> Subject: Re: Attributes 'Version and 'Body_Version X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Message-ID: NNTP-Posting-Host: 130.67.134.172 X-Complaints-To: news-abuse@nextra.no NNTP-Posting-Date: Thu, 08 Nov 2001 17:36:58 MET Organization: Nextra Public Access X-Trace: readme.online.no 1005237418 130.67.134.172 Date: Thu, 8 Nov 2001 17:34:27 +0100 Xref: archiver1.google.com comp.lang.ada:16068 Date: 2001-11-08T17:34:27+01:00 List-Id: Hi! In another development tool I worked on, we made a array of strings containing all files and their versions that were built into the executable. This array could be dumped into a file by a pushbutton in the "about" box. The array were populated by code in each source code file, this code was a part of the coding standard, and after it was initially there PVCS(configuration tool) was the only "one" worrying about it. I belive something similar can be done in Ada also. If you create a package that has logic administrating the array, and a function to set the array element this function could be called by all other packages' main block. One constraint I see is that purity pragmas can break this approach. Frank > If you're looking for a configuration management system, I suggest > using a configuration management system. If you want a version > indication in your package that gives you more information than > equality/inequality, it should be easy enough to add one yourself. > (For example, if you use RCS or CVS, you can have a version string > that's automatically updated whenever the source file is checked in.)