Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!uupsi!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.std.c Subject: Re: gcc and NULL function pointers. Message-ID: Date: 24 Jun 91 18:10:25 GMT References: <4728@inews.intel.com> <4796@inews.intel.com> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 19 In article <4796@inews.intel.com> bhoughto@hopi.intel.com (Blair P. Houghton) writes: > Do a global search-and-replace on the files, > especially if you ever expect to redistribute the code. Only to real computers. > That's why standard headers were invented, to be standard. Fine. ((void *)0) still conforms to the standard. > sed 's/\([^_A-Za-z]\)NULL\([^_A-Za-z]\)/\1(void *)NULL\2/g' Right. Boy, that's going to win friends and influence people. Plus, what do you think that'd do when I want to apply the next patch that comes from the net? Instead of grovelling around in code beforehand, I'll have to do it over and over again for every patch. -- Peter da Silva; Ferranti International Controls Corporation; +1 713 274 5180; Sugar Land, TX 77487-5012; `-_-' "Have you hugged your wolf, today?"