brandt at fokus.fraunhofer.de
Mon Oct 27 06:23:19 PST 2003
On Mon, 27 Oct 2003, Tony Finch wrote:
TF>On Mon, Oct 27, 2003 at 02:49:51PM +0100, Harti Brandt wrote:
TF>> According to ISO-C NULL is a symbol that
TF>> defines a null pointer so that:
TF>> execl(..., NULL)
TF>> appears to be legal, yet will probably cause failure on FreeBSD-sparc64.
TF>No, NULL is an implementation-defined null pointer constant, not a null
TF>pointer. The difference is that a null pointer constant is an integer
TF>constant expression that evaluates to zero (optionally cast to void*),
TF>and a null pointer is a null pointer constant converted to a pointer type
TF>(which might involve changes in representation). Therefore using a bare
TF>NULL to terminate the execl argument list is not in general legal.
Thanks, Tony. I found the relevant place (220.127.116.11). This sounds logical.
brandt at fokus.fraunhofer.de, harti at freebsd.org
More information about the freebsd-sparc64