Re: NULL and zeros
- From: Christopher Layne <clayne@xxxxxxxxxxxx>
- Date: Tue, 03 Oct 2006 11:53:44 -0700
Richard Heathfield wrote:
[defensive programming yadda yadda]
I meant it is *implied* and was not written because it wasn't relevant to the
discussion at hand.
Because the Standard requires it. This has long been established for char,
and the Committee, when asked to confirm or deny that it applied to all
integer types, confirmed that it does. So any conforming implementation
must get this right, even if it means doing bitty-box magic under the hood.
You clipped my last segment.
If a machine expressed integer 0 as all 1 bits internally, and I called
memset(&object, 0, sizeof(object)); that's going to result in object set to
all 0 bits?
.
- Follow-Ups:
- Re: NULL and zeros
- From: Richard Heathfield
- Re: NULL and zeros
- References:
- NULL and zeros
- From: Yevgen Muntyan
- Re: NULL and zeros
- From: Eric Sosman
- Re: NULL and zeros
- From: Yevgen Muntyan
- Re: NULL and zeros
- From: Eric Sosman
- Re: NULL and zeros
- From: Yevgen Muntyan
- Re: NULL and zeros
- From: Christopher Layne
- Re: NULL and zeros
- From: Yevgen Muntyan
- Re: NULL and zeros
- From: Richard Heathfield
- Re: NULL and zeros
- From: Christopher Layne
- Re: NULL and zeros
- From: Richard Heathfield
- Re: NULL and zeros
- From: Christopher Layne
- Re: NULL and zeros
- From: Richard Heathfield
- NULL and zeros
- Prev by Date: Re: NULL and zeros
- Next by Date: Re: About Visual C++ 2005 Express Edition
- Previous by thread: Re: NULL and zeros
- Next by thread: Re: NULL and zeros
- Index(es):
Relevant Pages
|