Date: Wed, 27 May 1998 21:35:19 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Eivind Eklund <eivind@yes.no> Cc: current@FreeBSD.ORG Subject: Replacing gcc as the system compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) Message-ID: <199805280135.VAA00687@khavrinen.lcs.mit.edu> In-Reply-To: <19980527225647.36082@follo.net> References: <19980527182337.47243@follo.net> <199805272004.WAA13789@ceia.nordier.com> <19980527225647.36082@follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Wed, 27 May 1998 22:56:47 +0200, Eivind Eklund <eivind@yes.no> said: > There is also what looks like a bug in handling of NULL - it doesn't > allow the use of ((void *)0) as NULL for function pointers. > I may remember the C standard incorrectly (I haven't looked it up), > but I think it is required to. As originally written, X3.159-1989 appeared to prohibit the behavior you want. I believe that this was the subject of an interpretation ruling (since you ought to be able to use NULL in the context of a function pointer regardless of its definition). I don't remember what the precise semantic result was, other than to allow the behavior you want. This is but one of the reasons I detest NULL.... -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805280135.VAA00687>