Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!dkuug!iesd!iesd.auc.dk!fischer From: fischer@iesd.auc.dk (Lars P. Fischer) Newsgroups: comp.std.c Subject: Re: gcc and NULL function pointers. Message-ID: Date: 18 Jun 91 20:08:09 GMT References: <16386@ganymede.inmos.co.uk> <1991Jun4.012914.25418@tkou02.enet.dec.com> <4641@inews.intel.com> Sender: news@iesd.auc.dk Organization: Mathematics and Computer Science, University of Aalborg Lines: 20 In-reply-to: peter@ficc.ferranti.com's message of 14 Jun 91 19:29:11 GMT >>>>> bhoughto@pima.intel.com (Blair P. Houghton) writes: Blair> The most general, and therefore most valuable, way to define NULL is Blair> to simply map it to the digit 0. >>>>> On 14 Jun 91 19:29:11 GMT, peter@ficc.ferranti.com (Peter da Silva) said: Peter> And you're working at Intel... On an 80x86 (x<3), there exist Peter> models where int = 16 bits, pointer = 32 bits. ... Oh, no, no, no. The NULL pointer war hits comp.std.c. Next thing we'll have a FAQ and Chris Torek will have to explain how to deal with NULL pointers once a month and .... Let's not create a new comp.lang.c. Please. /Lars -- Lars Fischer, fischer@iesd.auc.dk | It takes an uncommon mind to think of CS Dept., Univ. of Aalborg, DENMARK. | these things. -- Calvin