The SET_NON_ZERO_NULL macro is silly. On any arch where null pointers
are not represented as all zeroes, the null pointer value is still
*spelled* 0 in source code. CFOO *p = 0 always works, for all
values of FOO and all architectures.
If I'm missing something, please speak up.
--
Chip
On Fri, Mar 25, 2005 at 04:39:39PM -0500, Chip Salzenberg wrote:
The SET_NON_ZERO_NULL macro is silly. On any arch where null pointers
are not represented as all zeroes, the null pointer value is still
*spelled* 0 in source code. CFOO *p = 0 always works, for all
values of FOO and all
According to Nicholas Clark:
Is it being used as part of an optimisation? Is it so that memory for
structures can be allocated with calloc() (or later reset to all bits zero)
and then in the source to reset that structure a macro used to write
0 to all the pointers? On a platform where a NULL
