Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!think.com!yale!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: gcc and NULL function pointers.
Message-ID: <16381@smoke.brl.mil>
Date: 10 Jun 91 16:27:49 GMT
References: <1991Jun10.061202.25199@kithrup.COM> <1991Jun10.073125.25120@tkou02.enet.dec.com> <1991Jun10.081924.26439@kithrup.COM>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 5

In article <1991Jun10.081924.26439@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
>The header file would, therefore, be wrong.

No, Norman was right.  #define NULL 0 is always a proper way for an
implementation to define NULL in the standard headers.