🚀 go-pugleaf

"Nicolas Barbier" <reply@in.group.invalid> schreef in bericht
news:40fba9ab$0$8988$6c56d894@feed0.news.be.easynet.net...
> MaG wrote:
>
> > Null is niet altijd gelijk aan 0, hangt van de implementatie af.
>
> (NULL == 0) is implementatie-onafhankelijk steeds true. De mogelijke
> definities voor NULL zijn (void *) 0 en gewoon 0.
>

"The language definition states that for each pointer type, there is a
special value--the ``null pointer''--which is distinguishable from all other
pointer values and which is ``guaranteed to compare unequal to a pointer to
any object or function.'' That is, the address-of operator & will never
yield a null pointer, nor will a successful call to malloc. (malloc does
return a null pointer when it fails, and this is a typical use of null
pointers: as a ``special'' pointer value with some other meaning, usually
``not allocated'' or ``not pointing anywhere yet.'')
As mentioned above, there is a null pointer for each pointer type, and the
internal values of null pointers for different types may be different.
Although programmers need not know the internal values, the compiler must
always be informed which type of null pointer is required, so that it can
make the distinction if necessary."

Dus NULL is niet noodzakelijk 0 en je wordt niet geacht de waarde van de
NULL pointer te kennen.

Gebruik altijd NULL zou ik zo zeggen. ;-)

--- 

MaG