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,f19c50942e86e617
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: aliased variables
Date: 1998/08/14
Message-ID: <dewar.903075068@merv>#1/1
X-Deja-AN: 381008439
References: <35D264A8.FC025A5F@cmis.csiro.au>
 <ExM3wM.62q.0.-s@inmet.camb.inmet.com>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 903075153 18177 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1998-08-14T00:00:00+00:00
List-Id: <comp.lang.ada>

Richard may like better the error messages that come out of the latest
version of
GNAT:

     1. procedure Al_Exp is
     2.
     3.    type Mt is array(Natural range <>) of Integer;
     4.
     5.    type H_Mt is access all Mt;
     6.
     7.    K : aliased Mt(1 .. 10);
           |
        >>> warning: aliased object has explicit bounds
        >>> warning: declare with explicit initialization
        >>> warning: for use with unconstrained access

     8.    L : H_Mt;
     9.
    10. begin
    11.     L := K'Access;
                 |
        >>> object subtype must statically match designated subtype

    12. end;