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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,aaf4cd5313f652b1 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-01-24 07:55:42 PST Path: nntp.gmd.de!newsserver.jvnc.net!darwin.sura.net!gwu.edu!gwu.edu!not-for-mail From: mfeldman@seas.gwu.edu (Michael Feldman) Newsgroups: comp.lang.ada Subject: Re: type is access cf type is access all? Date: 24 Jan 1995 10:55:42 -0500 Organization: George Washington University Message-ID: <3g37tu$6cd@felix.seas.gwu.edu> References: <1995Jan20.114005.8916@vax.sbu.ac.uk> NNTP-Posting-Host: 128.164.9.3 Date: 1995-01-24T10:55:42-05:00 List-Id: In article <1995Jan20.114005.8916@vax.sbu.ac.uk>, wrote: > >What is the difference between: > > type FooPointers is access Foo; > >and > > type FooPointers is access all Foo; >My reading of this implies that omitting all will result >in variables the access type only being able to designate >dynamically (new) allocated anonymous variables and not >non-pool (aliased) variables. >A check of this idea on gnat 2.0 suggests that both types >can designate dynamic and aliased variables. >Anyone know the answer? Yeah, I bumped into this one too. It's a GNAT bug, simple as that. GNAT is missing the check that would normally prohibit the first type from desugnating aliuased variables. The NYU folks know about it; no need to report it to them. Mike Feldman