Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!eru!luth!sunic!mcsun!hp4nl!philapd!ssp11!dolf
From: dolf@idca.tds.PHILIPS.nl (Dolf Grunbauer)
Newsgroups: comp.lang.c
Subject: Re: Is "if (!pointer)" as portable as "if (pointer == NULL)" ???
Keywords: portability, pointers, NULL
Message-ID: <717@ssp11.idca.tds.philips.nl>
Date: 11 Apr 90 09:41:19 GMT
References: <656@hades.OZ> <1461@tkou02.enet.dec.com>
Organization: Philips Information Systems, Apeldoorn, The Netherlands
Lines: 19

In article <1461@tkou02.enet.dec.com> diamond@tkou02.enet.dec.com (diamond@tkovoa) writes:
<In article <656@hades.OZ> greyham@hades.OZ (Greyham Stoney) writes:
<
<>	if (buffer) free(buffer)
<
<This is also portable, and almost readable.  Again, to be really readable,
<you should still compare to NULL, but I grant that it would make your
<source code longer this time.

How about just a:
	free(buffer)

The manual pages I know allow a NULL pointer and doing nothing in this case.
Is this generally true ?
-- 
Dolf Grunbauer          Tel: +31 55 433233  Internet dolf@idca.tds.philips.nl
Philips Telecommunication and Data Systems  UUCP ....!mcsun!philapd!dolf
Dept. SSP, P.O. Box 245, 7300 AE Apeldoorn, The Netherlands         n   n   n
It's a pity my .signature is too small to show you my solution of  a + b = c