Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83 (MC830713); site edai.UUCP Path: utzoo!watmath!clyde!floyd!vax135!ukc!edcaad!edee!edai!ok From: ok@edai.UUCP (Richard O'Keefe) Newsgroups: net.lang.c Subject: Is #define NULL 0L ok? Message-ID: <4072@edai.UUCP> Date: Fri, 9-Mar-84 20:59:04 EST Article-I.D.: edai.4072 Posted: Fri Mar 9 20:59:04 1984 Date-Received: Mon, 12-Mar-84 05:42:25 EST Organization: Art.Intelligence,Edin.Univ. Lines: 21 One kind net.lang.c reader pointed out that Lint was JUSTIFIED in its complaints about my passing NULL to functions expecting a pointer argument. What I hadn't realise was that stdio.h defines #define NULL 0 (I thought it was (char*)0.) Now I know that there is no hope of ever running the program I've been struggling with on a 16- bit machine, the question is will it run on a machine with 32- bit pointers but int=16 bits. So I've changed my header file, it now starts #include#undef NULL #define NULL 0L This works fine on the VAX, but then so did NULL=0. Can any reader with a ptr=32&int=16 C compiler tell me if this is ok for such compilers? PS: my request for an ALIGNOK directive to Lint had nothing to do with *this* problem.