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-Thread: a07f3367d7,c6567772e9f3871d
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news2.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post02.iad.highwinds-media.com!news.flashnewsgroups.com-b7.4zTQh5tI3A!not-for-mail
From: Stephen Leake <stephen_leake@stephe-leake.org>
Newsgroups: comp.lang.ada
Subject: Re: organizing deep source trees with child packages
References: 
 <21c9e6bb-f4f7-4a00-bde7-68f2c1a42d01@q13g2000vby.googlegroups.com>
Date: Thu, 13 Oct 2011 04:20:12 -0400
Message-ID: <82ty7d1ewz.fsf@stephe-leake.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (windows-nt)
Cancel-Lock: sha1:bmXA/p5kYskCjBGHI1/9lhAO9cY=
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: abuse@flashnewsgroups.com
Organization: FlashNewsgroups.com
X-Trace: 323fb4e969f2fe029e66118934
Xref: g2news1.google.com comp.lang.ada:21409
Date: 2011-10-13T04:20:12-04:00
List-Id: <comp.lang.ada>

Greg Moncreaff <moncreg@gmail.com> writes:

> Have a 3 level (so far) tree of packages
>
> foo/bar/narf
>
> foo/foo.ads
> foo/bar/foo-bar.ads
> foo/bar/narf/foo-bar-narf.ads
> foo/bar/narf/foo-bar-narf-able.ads
> foo/bar/narf/foo-bar-narf-able.adb
> foo/bar/narf/foo-bar-narf-baker.ads
> foo/bar/narf/foo-bar-narf-baker.adb
> foo/bar/narf/foo-bar-narf-charlie.ads
> foo/bar/narf/foo-bar-narf-charlie.adb
>
> as you can see, the full paths of the items are visually silly, and
> somewhat painful if the tree needs refactoring

Drop the directory tree; use a flat directory with full file names:

foo/foo.ads
foo/foo-bar.ads
foo/foo-bar-narf.ads
foo/foo-bar-narf-able.ads
foo/foo-bar-narf-able.adb
foo/foo-bar-narf-baker.ads
foo/foo-bar-narf-baker.adb
foo/foo-bar-narf-charlie.ads
foo/foo-bar-narf-charlie.adb


> e.g. I would like something like
>
> foo/bar/narf/narf-able.ads
> foo/bar/narf/narf-able.adb
> foo/bar/narf/narf-baker.ads
> foo/bar/narf/narf-baker.adb
> foo/bar/narf/narf-charlie.ads
> foo/bar/narf/narf-charlie.adb

Is that better than my suggestion? If so, why?

In my view, directories are for very large groupings of files; I often
have hundreds of Ada files in one directory.

> foo/bar/narf/narf.ads could define
>
> package Narf renames Foo.Bar.Narf

I think this is a name conflict, but you could use:

package Narf_Local renames Foo.Bar.Narf

which is probably not worth it.

-- 
-- Stephe