[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dpkg semi-hijack - an announcement (also, triggers)

On Sun, Mar 09, 2008 at 06:34:36PM +0000, Ian Jackson wrote:
> Pierre Habouzit writes ("Re: dpkg semi-hijack - an announcement (also, triggers)"):
> >   If you're so afraid that one of the included headers defines NULL to
> > '0', then just assert (__builtin_types_compatible(NULL, void *))
> > somewhere and be done with it. But please, (char *)0 is not only wrong,
> > it's also tasteless and ugly to the eye.

> In what way is (char*)0 wrong in these contexts ?

According to execlp manpage:

	The list of arguments must be terminated by a NULL pointer,
	and, since these are vari‐adic functions, this pointer _must_
	be cast (char *) NULL.

"rm -rf" only sounds scary if you don't have backups

Reply to: