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: 7 Jul 93 21:07:08 GMT
From: cis.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!howland.
reston.ans.net!usc!cs.utexas.edu!convex!convex!pelakh@ucbvax.Berkeley.EDU  (Bor
is Pelakh)
Subject: Re: Question of Visibility
Message-ID: <1993Jul7.210708.5853@news.eng.convex.com>
List-Id: <comp.lang.ada>

In article <C9t9Ly.EML@inmet.camb.inmet.com> stt@spock.camb.inmet.com (Tucker T
aft) writes:
>>The user has a large body of code interfacing to a FORTRAN library. FORTRAN
>>requires .TRUE. = ~.FALSE. in a bit-wise way. They wanted to change the
>>meaning of BOOLEAN throughout their entire source by introducing the type
>>into one of the root packages, and not having to edit any of the other code.
>
>I would recommend that your user just rename "boolean" to "bool" or 
>"f77_bool" or equivalent.  

Actually, the solution they finally accepted was to put 

	subtype boolean is boolean_pkg.boolean;

in the units where the type was necessary.

-- 
Boris Pelakh		Ada Project Leader          pelakh@convex.com
		     Convex Computer Corporation
"If winning isn't important, why keep score ?"	-- Lt. Worf, Star Trek TNG.