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,e34c4a65968f0dd,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1993-03-23 05:31:16 PST
Newsgroups: comp.lang.ada
Path: 
 sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!news.sei.cmu.edu!ajpo.sei.cmu.edu!brosgol
From: brosgol@ajpo.sei.cmu.edu (Benjamin Brosgol)
Subject: Occurrences of Long_Integer in ADAR Software
Message-ID: <1993Mar23.004551.19464@sei.cmu.edu>
Sender: netnews@sei.cmu.edu (Netnews)
Organization: Software Engineering Institute
Date: Tue, 23 Mar 1993 00:45:51 EST
Date: 1993-03-23T00:45:51-05:00
List-Id: <comp.lang.ada>

Several recent postings have referred to occurrences of Long_Integer
in the ADAR distribution software, so a clarification is in order.
The software consists of two parts: the ADAR units (specs and bodies),
and a set of program examples.  There are no uses of Long_Integer (nor
Long_Float) in the ADAR units themselves.  However, one of the
examples instantiates an ADAR generic package with Long_Integer (and
also with Long_Float) in order to exploit the target machine's
arithmetic capacity.  Other example programs similarly refer to these
types.  The next release should either avoid or at least document
these uses of such potentially non-portable types so that users
understand more clearly what needs to be modified.

Ben Brosgol