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,ec2b9b815bd3b0bd
X-Google-Attributes: gid103376,public
From: mfb@mbunix.mitre.org (Michael F Brenner)
Subject: Re: Conditional Code in Ada 95?
Date: 1998/08/24
Message-ID: <6rrtuf$cqg@top.mitre.org>#1/1
X-Deja-AN: 384202097
References: <35DDFB42.1311@boeing.com> <2$$CdIjQwTPX@nedcu4>
Organization: The MITRE Corporation, Bedford Mass.
Newsgroups: comp.lang.ada
Date: 1998-08-24T00:00:00+00:00
List-Id: <comp.lang.ada>

>> I just saw some Ada95 code riddled with conditional
>> compilation statements. I wasn't aware that this
>> was part of Ada95 and I can't find it in the ARM.

> Fortunately... The clean (and compatible) way remains
> hardware-specific units when needed and, within an unit,
> constants like ...

Yes, constants are good for executable statements. However, there is
no way WITHIN the Ada language to select which of the hardware
specific bodies to use with a multi-platform package.

This is to be considered a requirement for Ada 200X.