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,4c019ad9cc913bbe X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-09-19 08:40:45 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!hammer.uoregon.edu!skates!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: The Dreaded "Missing Subunits" Date: 19 Sep 2002 11:33:53 -0400 Organization: NASA Goddard Space Flight Center (skates.gsfc.nasa.gov) Message-ID: References: <1b585154.0209121449.ef12609@posting.google.com> NNTP-Posting-Host: anarres.gsfc.nasa.gov Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: skates.gsfc.nasa.gov 1032450251 17509 128.183.220.71 (19 Sep 2002 15:44:11 GMT) X-Complaints-To: usenet@news.gsfc.nasa.gov NNTP-Posting-Date: 19 Sep 2002 15:44:11 GMT User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.ada:29182 Date: 2002-09-19T15:44:11+00:00 List-Id: Dmitry A.Kazakov writes: > Preben Randhol wrote: > > Come on what is so nasty with .adb .ads? > > Not so nasty if you start a new project. But I remember how it took two > days or so to rename all files while porting a project from DEC Ada to > GNAT. It was not only file extensions. For the sake of portability all > files names were 8-letters long. Well, it appeared a little bit less > portable than we expected! (:-)) gnatchop would solve that problem easily; perhaps it was not available then. It would be nice if every vendor provided a similar tool; "take this collection of randomly named files and name them according to your convention". > > Besides don't you get the with-ing problem with .ada? Depends on wether the spec and body are both in one file, or you still have two files, just both ending in .ada. If you have two files, then you still need some convention to distinguish the body from the spec; hence Rationals foo.1.ada, foo.2.ada. If you have one file, you lose the separate compilation of spec and body. You don't get horrible "withing" problems (Ada is still the same language), you just get horrible recompilation times (you recompile the spec and everything that depends on it, every time you change the body). > Why? It worked with Ada 83, why shouldn't it with Ada 95. In Ada 83 you still needed different file names for the spec and body. The convention I used with DEC 83 (if I recall correctly) was foo_s.ada for the spec, and foo.ada for the body. I much prefer foo.ads, foo.adb. You could put both spec and body in one file, but you got the same horrible recompilation issues. -- -- Stephe