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
X-Google-Thread: 103376,ec2b9b815bd3b0bd
X-Google-Attributes: gid103376,public
From: "Jean-Pierre Rosen" <rosen.adalog@wanadoo.fr>
Subject: Re: Conditional Code in Ada 95?
Date: 1998/08/25
Message-ID: <6s0fcl$3gj$1@platane.wanadoo.fr>#1/1
X-Deja-AN: 384850840
Content-Transfer-Encoding: 8bit
References: <35DDFB42.1311@boeing.com> <2$$CdIjQwTPX@nedcu4>
 <6rrtuf$cqg@top.mitre.org>
Content-Type: text/plain; charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Organization: Adalog
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1998-08-25T00:00:00+00:00
List-Id: <comp.lang.ada>


Michael F Brenner a �crit dans le message <6rrtuf$cqg@top.mitre.org>...
>>> 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.


However, there is something that's damn close to it:

with Hardware_Specific_1;
package Hardware_Specific renames Hardware_Specific_1;

and then use package Hardware_Specific all over the place. If you change
hardware, there is one line to change in the whole program.