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=0.7 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no
	version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uunet!ns-mx!herky.cs.uiowa.edu!bonak
From: bonak@herky.cs.uiowa.edu (Esmail Bonakdarian)
Newsgroups: comp.lang.ada
Subject: Is this a (Meridian) compiler bug?
Message-ID: <5385@ns-mx.uiowa.edu>
Date: 8 Apr 91 22:22:36 GMT
Sender: news@ns-mx.uiowa.edu
Reply-To: bonak@herky.cs.uiowa.edu (Esmail Bonakdarian)
Organization: U of Iowa, Iowa City, IA
List-Id: <comp.lang.ada>

It the following subtype declaration (line 3) legal?  The LRM seems to
specify a type_mark after the 'is' reserved word (and an optional
constraint).
 
The Meridian compiler compiles this code without any problems though the
Telesoft compiler I have access to does not like it. I can fix the code by
changing line 3 to
 
subtype ROW_TYPE is INTEGER range 1 .. ROWS;
 
Am I reading the LRM incorrectly or have I stumbled across a bug in this
compiler? I would like somebody to confirm this for me before I contact
Meridian (by the way, do they have an e-mail address?).
 
Thanks.
 
Esmail
------------------
    Meridian AdaVantage v4.1  Source file: bug.ada  Page 1
    Sun Apr  7 1991 19:25:17
 
 
        1  procedure BUG is
        2
        3  ROWS: constant := 5;
        4
        5  subtype ROW_TYPE is 1 .. ROWS;
        6
        7  begin
        8    null;
        9  end;
 
    Compilation Summary
         Ada library used: ada.lib
         Compile options:
           (none)
         9 lines compiled.
         9 lines listed.
         No errors detected.
         No warnings reported.