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,
	REPLYTO_WITHOUT_TO_CC autolearn=no 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!news.glorb.com!news-out.readnews.com!transit3.readnews.com!s09-10.readnews.com!unm2.readnews.com.POSTED!not-for-mail
X-Trace: 
 DXC=`IQSW_k[CFo]X2QhPiQh[f[3OhcoN[H0`X44`8^\]>7j8DHB_I2k0T`<?2oYhQm10h[A9>WLFJOkc24DKT5NOBkgJG?IXdh5TQ`alM@JQSKSId
X-Complaints-To: abuse@ngroups.net
Date: Thu, 13 Oct 2011 06:21:05 +0200
From: Per Sandberg <per.sandberg@bredband.net>
Reply-To: per.sandberg@bredband.net
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.22) Gecko/20110906 Fedora/3.1.14-1.fc14 Thunderbird/3.1.14
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: organizing deep source trees with child packages
References: 
 <21c9e6bb-f4f7-4a00-bde7-68f2c1a42d01@q13g2000vby.googlegroups.com>
In-Reply-To: 
 <21c9e6bb-f4f7-4a00-bde7-68f2c1a42d01@q13g2000vby.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <4e966737$0$20238$a8266bb1@newsreader.readnews.com>
Organization: readnews.com - News for Geeks and ISPs
NNTP-Posting-Host: c27773f7.newsreader.readnews.com
Xref: g2news1.google.com comp.lang.ada:21406
Date: 2011-10-13T06:21:05+02:00
List-Id: <comp.lang.ada>

Why Java naming conventions ??
/Per

On 10/13/2011 01:38 AM, Greg Moncreaff wrote:
> 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
>
> is there some way of renaming the parent package along the way to
> tighten up the names?,
> without having to have naming blocks in the .gpr files?
>
> 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
>
> if by some magic
>
> foo/bar/narf/narf.ads could define
>
> package Narf renames Foo.Bar.Narf
>
> and then
>
> foo/bar/narf/narf.ads could be
>
> package Narf.Able is ...
>
>
> or is this hopeless desire and an exercise with no value?