X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Mon, 2 Aug 2004 18:41:58 +0200
From: Egon Eckert <egon AT heaven DOT industries DOT cz>
To: djgpp AT delorie DOT com
Subject: Re: assembly code of the "strange error" - program
Message-ID: <20040802164158.GG31986@webhome.cz>
References: <WcpNc.640$zS6 DOT 86489 AT news02 DOT tsnz DOT net> <20040727070949 DOT 29244 DOT 00000306 AT mb-m19 DOT aol DOT com> <pnxNc.667$zS6 DOT 95084 AT news02 DOT tsnz DOT net> <410D7A24 DOT 1306F0C1 AT yahoo DOT com> <2n74llFts6lmU1 AT uni-berlin DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2n74llFts6lmU1@uni-berlin.de>
User-Agent: Mutt/1.5.5.1+cvs20040105i
Sender: Egon Eckert <egon AT webhome DOT cz>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Close but not quite correct, I think. It's actually  guaranteed to
> be initialized to all contained objects equalling their particular flavour
> of zero.  That's often the same as all bytes zero, but it doesn't have
> to be.

Huh?  What do you mean?  Something like

double a;

may be == 0.0, but not necessarily all bytes zero?  Or something more
obscure, without practical implications on common, modern hardware?  Any
examples?

-- 
Egon Eckert, Heaven Industries, s.r.o.
E-mail: egon AT heaven DOT industries DOT cz

Never be afraid to try something new. Remember, amateurs built the
ark; professionals built the Titanic. -- Anonymous