From: Gautier <gautier.demontmollin@maths.unine.ch>
Subject: Re: Redefining Integer Type ...
Date: 2000/10/18
Date: 2000-10-18T00:00:00+00:00 [thread overview]
Message-ID: <39EDAA8F.55FC6F3E@maths.unine.ch> (raw)
In-Reply-To: wccn1g2cnfb.fsf@world.std.com
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.
next prev parent reply other threads:[~2000-10-18 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-18 0:00 Redefining Integer Type Arnaud de Muyser
2000-10-18 0:00 ` Robert A Duff
2000-10-18 0:00 ` Gautier [this message]
2000-10-18 0:00 ` Pat Rogers
2000-10-18 0:00 ` Robert A Duff
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox