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: a07f3367d7,556e5b18154df788 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.224.207.2 with SMTP id fw2mr3506578qab.6.1365342759678; Sun, 07 Apr 2013 06:52:39 -0700 (PDT) Path: ef9ni13649qab.0!nntp.google.com!border1.nntp.dca.giganews.com!backlog1.nntp.ams.giganews.com!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!xlned.com!feeder7.xlned.com!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!news.n-ix.net!news.hufnagl.info!fu-berlin.de!feeder.erje.net!eu.feeder.erje.net!usenet.blueworldhosting.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post02.iad.highwinds-media.com!news.flashnewsgroups.com-b7.4zTQh5tI3A!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: Interresting, possibly buggy behavior in GNAT generics w/ expression function. References: <65330bfe-39e4-4f7b-85f5-e06e9458bf29@googlegroups.com> Date: Tue, 02 Apr 2013 07:14:30 -0400 Message-ID: <85k3olb2w9.fsf@stephe-leake.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (windows-nt) Cancel-Lock: sha1:grKbQi5c6uetlP6oWwfXlgJBqHA= MIME-Version: 1.0 X-Complaints-To: abuse@flashnewsgroups.com Organization: FlashNewsgroups.com X-Trace: a9bf0515abd97ede7d80114090 X-Received-Bytes: 1473 X-Original-Bytes: 1790 Content-Type: text/plain Date: 2013-04-02T07:14:30-04:00 List-Id: "Randy Brukardt" writes: > "Adam Beneschan" wrote in message > news:65330bfe-39e4-4f7b-85f5-e06e9458bf29@googlegroups.com... > On Friday, March 29, 2013 6:04:28 PM UTC-7, Randy Brukardt wrote: > > ... >>Randy, it looks to me that the original code called Image(...) only from >>inside the >>generic specification or body, not outside. > > OK, I didn't see that, because the OP I got only had a description of the > spec in it, no code at all. The code is in function expressions in the spec; no body required. -- -- Stephe