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: 103376,2bcab3f121e1e3a7,start
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.66.233 with SMTP id i9mr2390492pbt.28.1316522927892;
        Tue, 20 Sep 2011 05:48:47 -0700 (PDT)
Path: 
 lh7ni1119pbb.0!nntp.google.com!news1.google.com!news2.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!feedme.ziplink.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Optional body for nested generic
Date: Tue, 20 Sep 2011 13:48:48 +0100
Organization: A noiseless patient Spider
Message-ID: <m262kn2xcf.fsf@pushface.org>
Mime-Version: 1.0
Injection-Info: mx04.eternal-september.org;
 posting-host="dFCm8HWntFqmDIilBLqEJQ";
	logging-data="7048"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+I2vCj5Zv0RrAd4qnNXbgRN1hawPvi/sk="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (darwin)
Cancel-Lock: sha1:iW+kVU+T2Kzsy51v6YO4Vuqgs1c=
	sha1:Nyvgz8mj1efiYicy0btOs7GzkvY=
Xref: news1.google.com comp.lang.ada:18046
Content-Type: text/plain; charset=us-ascii
Date: 2011-09-20T13:48:48+01:00
List-Id: <comp.lang.ada>

I was surprised to find that GNAT makes it optional to have a body for a
nested generic package (in the code below, gpack1 has an empty body,
gpack2 doesn't have a body at all).

package Pack is
   pragma Elaborate_Body;
   generic
   package Gpack1 is
      procedure Proc;
      pragma Import (C, Proc, "proc");
   end Gpack1;
   generic
   package Gpack2 is
      procedure Proc;
      pragma Import (C, Proc, "proc");
   end Gpack2;
end Pack;

package body Pack is
   package body Gpack1 is
   end Gpack1;
end Pack;

I suppose that the reasoning for disallowing unrequired bodies (roughly,
making it impossible to obsolete the ada library by adding/removing
something with no other impact) only applies at library level, where
there's a correspondence to a file?