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=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!gandalf.srv.welterde.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.rrsoftware.com!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: Trivia: Ada packages are great!
Date: Sun, 11 Nov 2018 01:01:17 -0600
Organization: JSA Research & Innovation
Message-ID: <ps8k3t$g1i$1@franka.jacob-sparre.dk>
References: <5af3c4a0-5856-47ec-bb05-0ae9f9bb24ff@googlegroups.com>
 <0c992f78-0496-4d8c-b046-fd75aae32599@googlegroups.com>
 <f57a37a4-9557-40d8-8f4f-1d97751fe4ea@googlegroups.com>
Injection-Date: Sun, 11 Nov 2018 07:01:18 -0000 (UTC)
Injection-Info: franka.jacob-sparre.dk;
 posting-host="rrsoftware.com:24.196.82.226";
	logging-data="16434"; mail-complaints-to="news@jacob-sparre.dk"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.7246
Xref: reader02.eternal-september.org comp.lang.ada:54812
Date: 2018-11-11T01:01:17-06:00
List-Id: <comp.lang.ada>


"Maciej Sobczak" <see.my.homepage@gmail.com> wrote in message 
news:f57a37a4-9557-40d8-8f4f-1d97751fe4ea@googlegroups.com...
...
> GNAT accepts this with Test as a starting point. No
> specification files, no packages. Even "with Foo;" works fine
> without any separate spec file.
> Hey, we are closer to the obfuscated Ada context!

Sure, but the names of compilation units still have to be unique -- no 
overloading is allowed. So there still can be used to unambigiously name 
things. Ada 83 was designed carefully so that nearly(*) everything can be 
named with a full expanded name starting with the compilation unit. That was 
done in particular to help with "programming-in-the-large", and specifically 
to help with integration of large packages. There is always a way to work 
around an integration conflict without restructuring anything. (Whether 
restructuring would be a better idea is a separate issue, of course.) Of 
course, if people avoided

(*) Items in unnamed blocks and loops don't have full expanded names, but 
since these are local by nature they hardly ever are involved in an 
integration conflict. That's more of a problem for language-defined images 
(of exceptions and tags, in particular).

                                              Randy.