Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!menudo.uh.edu!lobster!sugar!ficc!peter
From: peter@ficc.ferranti.com (Peter da Silva)
Newsgroups: comp.std.c
Subject: Re: gcc and NULL function pointers.
Message-ID: <IB8C2EC@xds13.ferranti.com>
Date: 28 Jun 91 17:42:35 GMT
References: <25572@well.sf.ca.us> <1146.Jun2221.20.2291@kramden.acf.nyu.edu> <16506@smoke.brl.mil> <17605.Jun2607.39.3591@kramden.acf.nyu.edu> <1991Jun27.190107.627@cirrus.com>
Reply-To: peter@ficc.ferranti.com (Peter da Silva)
Organization: Xenix Support, FICC
Lines: 10

In article <1991Jun27.190107.627@cirrus.com> dhesi@cirrus.com (Rahul Dhesi) writes:
>      ((void *) 0) is ANSI-conformant but wrong.
>      ((char *) 0) is not ANSI-conformant and wrong.
>      All definitions of NULL other than 0 are wrong, no matter how
>      much or how little ANSI-conformant they may be.

Sorry, that's wrong.
-- 
Peter da Silva; Ferranti International Controls Corporation; +1 713 274 5180;
Sugar Land, TX  77487-5012;         `-_-' "Have you hugged your wolf, today?"