From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 5 Feb 93 15:38:40 GMT
From: eachus@mitre-bedford.arpa  (Robert I. Eachus)
Subject: Re: Help with Meridian compiler, please
Message-ID: <EACHUS.93Feb5103840@dr_no.mitre.org>
List-Id: <comp.lang.ada>

In article <1993Feb4.144224.7460@goya.uu.es> aalvarez@dit.upm.es (Angel Alvarez
) writes:

   >  a: NATURAL range 0..1:=0;

    Ooooh Ouch!  Tricky syntax analyzer test!  To make it harder use 

    A: Natural range 0..2:=0;

    The reason Meridan trips up (and yes it is a compiler bug) is
probably that 2:1101: is a legal numeric literal (with a decimal value
of 13).  I suspect that the compiler starts reading with the syntax of
an integer literal and when that fails backs up incorrectly, reading
the value 1 correctly but losing the colon.


					Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...
--

					Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...