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.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,72d0d0a56877b2ed,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-09-25 02:19:06 PST
Path: bga.com!news.sprintlink.net!demon!hacker!hacker.demon.co.uk!steve
From: steve@hacker.demon.co.uk (Stephen M. Youndt)
Newsgroups: comp.lang.ada
Subject: Ada83 or DEC Ada: Feature or bug?
Date: 24 Sep 1994 05:45:03 GMT
Organization: "Hacker at Large"
Distribution: world
Message-ID: <360ecv$kq1@hacker.demon.co.uk>
NNTP-Posting-Host: hacker.demon.co.uk
Date: 1994-09-24T05:45:03+00:00
List-Id: <comp.lang.ada>

Is it a feature of Ada83 or DEC Ada that makes it impossible to work with
unsigned values? MAX_INT always bites back with CONSTRAINT_ERROR when I try
to do any real work with unsigned 32bit values (i.e. SYSTEM.UNSIGNED_LONGWORD).
Both I and my coworkers find this terribly annoying. Is this part of Ada83
or a DEC Ada peculiarity? If Ada83, will it be fixed in 9X?

Thanks,
Steve
-- 
Stephen M. Youndt   * Inet: steve@hacker.demon.co.uk  * CIS: 73121,3407
                    *     Tel: +44 242 863 028        *