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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.42.82.79 with SMTP id c15mr6665924icl.7.1406278331263; Fri, 25 Jul 2014 01:52:11 -0700 (PDT) X-Received: by 10.140.86.105 with SMTP id o96mr14828qgd.11.1406278331227; Fri, 25 Jul 2014 01:52:11 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!feeder.erje.net!eu.feeder.erje.net!news.glorb.com!h18no7243546igc.0!news-out.google.com!j6ni12934qas.0!nntp.google.com!v10no2408620qac.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 25 Jul 2014 01:52:11 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=91.55.222.226; posting-account=rmHyLAoAAADSQmMWJF0a_815Fdd96RDf NNTP-Posting-Host: 91.55.222.226 References: <33af85fe-a92c-415a-b6aa-c658d95ca18c@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <6fd2e985-1a41-442e-a6c8-6a9f90960e94@googlegroups.com> Subject: Re: Should be in the root package or its child? From: AdaMagica Injection-Date: Fri, 25 Jul 2014 08:52:11 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: news.eternal-september.org comp.lang.ada:21200 Date: 2014-07-25T01:52:11-07:00 List-Id: On Thursday, July 24, 2014 6:21:40 PM UTC+2, Victor Porton wrote: > package RDF.Raptor is > > end RDF.Raptor; What do you gain with an empty package? > But on the other hand, things become more finely classified if I use child > packages. That's OK, this is the purpose of child packages. But again, what do gain with an empty top package and having the world in a child, especially if every user has to with it? > So, do you insist, that it should not be in a child library package? No, I don't insist - after all, it's your code.