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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,baa6871d466e5af9 X-Google-Attributes: gid103376,public From: bobduff@world.std.com (Robert A Duff) Subject: Re: AQ&S Guidance on pragma Elaborate_Body Date: 1997/04/26 Message-ID: #1/1 X-Deja-AN: 237562681 References: <528878564wnr@diphi.demon.co.uk> <01bc5250$db1b6c00$28f982c1@xhv46.dial.pipex.com> Organization: The World Public Access UNIX, Brookline, MA Newsgroups: comp.lang.ada Date: 1997-04-26T00:00:00+00:00 List-Id: In article <01bc5250$db1b6c00$28f982c1@xhv46.dial.pipex.com>, Nick Roberts wrote: >It's a nice idea. The problem with this idea, though (I think), is that >there are no operations defined for Q.T for use in the body of procedure >Op. What is Op able to do with the parameter OT? Anything? Various ideas along these lines were discussed here a year or two ago. Basically, the idea would be that the spec can't do much of anything with the imported type -- it's more-or-less like an incomplete type. Declare access-to-OT'Class parameters, and perhaps not much more. The body would then do a normal with_clause, and could therefore see all the operations of OT. - Bob