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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,53ca16c587912bce X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Source files organisation using gnat Date: 1997/07/04 Message-ID: #1/1 X-Deja-AN: 254704032 References: <19970630185901.OAA27670@ladder02.news.aol.com> <33B93E87.59E2@hso.link.com> Organization: New York University Newsgroups: comp.lang.ada Date: 1997-07-04T00:00:00+00:00 List-Id: Samuel Harris says <> Goodness, of *course* one does not expect a large development project to use a single directory, absolutely not. One of the advantages of the GNAT source based approach is precisely that you can conveniently use a typical hierarchical directory structure to arrange your sources. <> I am a little surprised by this statement. It seems like the only sources in this category are the gnat.* units, which is a small set of units, not often used. For these, I agree, an HTML version is a good idea. For the Ada units, I would think that an HTML version of the reference manual is a much better source of information than looking at the GNAT sources. In any case, if you *do* want to look at any of the GNAT sources in gnatlib, it is *much* more convenient that they are in a single flat space, since you would always be searching by name in any case.