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,1c4a54744b1a13e2
X-Google-Attributes: gid103376,public
From: Gautier <gautier.demontmollin@maths.unine.ch>
Subject: Re: Redefining Integer Type ...
Date: 2000/10/18
Message-ID: <39EDAA8F.55FC6F3E@maths.unine.ch>#1/1
X-Deja-AN: 682878187
Content-Transfer-Encoding: 7bit
References: <39ED8FE6.3F7CF3B9@attol-testware.com>
 <wccn1g2cnfb.fsf@world.std.com>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
X-Trace: 18 Oct 2000 15:50:09 +0100, mac13-32.unine.ch
Organization: Maths - Uni =?iso-8859-1?Q?Neuch=E2tel?=
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Date: 2000-10-18T00:00:00+00:00
List-Id: <comp.lang.ada>

Robert A Duff:

> Names from outer scopes always take precedence over use-visible names.
> Everything is nested within Standard.  So in your example,
> Standard.Integer hides Pack.Integer.
> 
> I don't like that rule -- it's error prone, as you can see.
> Hiding considered harmful.
> 
> A good rule of thumb is to never redefine any name (such as Integer)
> that is declared in Standard, or *could* be declared in Standard (such
> as Long_Long_Long_Long_Long_Integer).

I have tested some time ago "type boolean is (true,false);": different
compilers made it work in differents ways, without warning... :-)

G.