On Thu, 28 May 1998, Pete Ryland wrote:

>ok - this is often confused.  the c faq has a *big* section on this...
>
>NULL should be defined as 0.

Ok.

>0 cast to a pointer type is defined as an undefined pointer and can be
>implemented by the compiler as any number (including -1, or something

This sound me a little strange. I think that if I use (void *)0 the
compiler must use 0 not -1. If ANSI-C declare that a NULL pointer is a
(void *)0 is another story. I' d like if somebody could confirm that I am
wrong. 

>will give the same results on any system that is ANSI-C.  There are no
>problems with portability, even on systems that have non-zero null 
>pointers.

Ok, I understood this and this is not more an issue at least for me.

Andrea[s] Arcangeli

Reply via email to