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!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!feeder.erje.net!eu.feeder.erje.net!bloom-beacon.mit.edu!bloom-beacon.mit.edu!newsswitch.lcs.mit.edu!nntp.TheWorld.com!.POSTED!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: GNAT GPL is not shareware Date: Wed, 14 Jan 2015 18:43:45 -0500 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <87bnmetex4.fsf@ludovic-brenta.org> <1otenmcbgnvlt$.dn9361nl2jm8$.dlg@40tude.net> <8ryfky4awox2$.q2gfw4pvsgau.dlg@40tude.net> NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: pcls7.std.com 1421279024 20666 192.74.137.71 (14 Jan 2015 23:43:44 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Wed, 14 Jan 2015 23:43:44 +0000 (UTC) User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix) Cancel-Lock: sha1:vSmcAtUQefCJxyZRTA85wKyMcvQ= Xref: news.eternal-september.org comp.lang.ada:24574 Date: 2015-01-14T18:43:45-05:00 List-Id: "J-P. Rosen" writes: > Since you can't statically know what subprogram is being called, Well, you can't know which body will be dispatched to, but formally speaking, the subprogram being calling is known statically (and might be abstract). > Corresponding_Called_Entity returns Nil_Element in place of the > subprogram declaration. Hmm. That seems like just a design mistake in ASIS. It seems like it should return the entity denoted by the name in the call (which always exists statically -- X.all(...) is never a dispatching call). That is, Corresponding_Called_Entity should return what you say about Corresponding_Called_Root_Entity below. But I think you can work around the problem -- look at the name of the call and see what it denotes. >...But without a declaration, you cannot know the > formal parameters (so no information about the modes, whether some > parameters are defaulted, etc.) Right. That sort of thing is an annoying nuisance. > We need a Corresponding_Called_Root_Entity... I think Serguei added > something like that. I searched for "function Corresponding_Called", and didn't see anything like that. So if we have such a thing, it has a different name. Are you sure you didn't end up working around the problem in the way I suggested above? - Bob