From:	Dag Nummedal <nummedal AT pvv DOT unit DOT no>
Date:	Thu, 3 Nov 94 18:49:58 +0100
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: NULL pointers...
References:	<199411020253 DOT UAA24570 AT agassiz DOT cas DOT und DOT NoDak DOT edu>
	<199411020624 DOT BAA175566 AT acs4 DOT bu DOT edu>

pjones AT acs DOT bu DOT edu writes:
 > > Charles Sandmann says:
 > > 
 > > Probably the easiest fix would be to change the NULL pointer to
 > > something way out of range, like maybe: 0xffffffff.  It may break some
 > 
 > Hmm...  I would guess that having NULL != (void *) 0, even if it's not
 > supposed to be guaranteed to be that in the first place, would break more code
 > than we'd all like to imagine.

Actually the above cast, and (char *)0, (int *)0 etc. would still work.

Something like: long l = 0; void * p = (void *)l would break, but that is
seriously buggy code anyway.

Null pointers to vararg functions would probably be the greatest problem.

-Dag Nummedal

- Raw text -