From owner-freebsd-current Wed May 27 18:35:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26925 for freebsd-current-outgoing; Wed, 27 May 1998 18:35:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26902 for ; Wed, 27 May 1998 18:35:26 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id VAA00687; Wed, 27 May 1998 21:35:19 -0400 (EDT) (envelope-from wollman) Date: Wed, 27 May 1998 21:35:19 -0400 (EDT) From: Garrett Wollman Message-Id: <199805280135.VAA00687@khavrinen.lcs.mit.edu> To: Eivind Eklund Cc: current@FreeBSD.ORG Subject: Replacing gcc as the system compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) In-Reply-To: <19980527225647.36082@follo.net> References: <19980527182337.47243@follo.net> <199805272004.WAA13789@ceia.nordier.com> <19980527225647.36082@follo.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < 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