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,30f8e9ec3e840189 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-09-11 23:11:01 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!212.74.64.35!colt.net!dispose.news.demon.net!news.demon.co.uk!demon!pogner.demon.co.uk!zap!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: avl tree - booch components Date: 11 Sep 2001 06:53:41 +0100 Organization: CodeFella Message-ID: References: <20010907091153.12625104.tonygair@nospam.blueyonder.co.uk> NNTP-Posting-Host: localhost X-NNTP-Posting-Host: pogner.demon.co.uk:158.152.70.98 X-Trace: news.demon.co.uk 1000275005 nnrp-08:9305 NO-IDENT pogner.demon.co.uk:158.152.70.98 X-Complaints-To: abuse@demon.net NNTP-Posting-Date: 11 Sep 2001 05:53:41 GMT X-Newsreader: Gnus v5.7/Emacs 20.7 Xref: archiver1.google.com comp.lang.ada:13039 Date: 2001-09-11T05:53:41+00:00 List-Id: Stephen Leake writes: > Hmm. I agree it would be nice if you could have both CVS $Id$ and no > warnings from the GNAT style check. However, given a choice between > the two, I'll take the no warnings. I will adopt a style like -- $RCSfile: bc-containers-collections-ordered-bounded.ads,v $ -- $Revision: 1.5 $ -- $Date: 2001/09/11 05:29:27 $ -- $Author: simon $ (I don't _think_ the RCSfile is likely to break the limit) > Do you ever actually read the output of CVS $Id$ ? What is it actually > used for? At a pinch I suppose RCSfile and Revision would be the minimum, but I find the date very useful too especially when not connected to the repository. What file is this? what version? when did it last change? who changed it? are all important. The last particularly so given multiple users. I know it's all available from the repository (cvs status; cvs log) but still .. > Ignoring warnings in general is very bad practice, and it's too easy > to go from "well, _this_ warning is ok" to "I checked all the warnings > last week, I'll ignore them this time" to "just ignore the warnings". How very true!