Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!brl-tgr!ron
From: ron@brl-tgr.ARPA (Ron Natalie <ron>)
Newsgroups: net.lang.c
Subject: Re: Must a NULL pointer be a 0 bit patte
Message-ID: <5616@brl-tgr.ARPA>
Date: Mon, 5-Nov-84 13:01:34 EST
Article-I.D.: brl-tgr.5616
Posted: Mon Nov  5 13:01:34 1984
Date-Received: Wed, 7-Nov-84 01:00:19 EST
References: <102@ISM780B.UUCP>
Organization: Ballistic Research Lab
Lines: 20

> >/* Written 12:37 pm  Oct 22, 1984 by ron@brl-tgr in ISM780B:net.lang.c */
> >> It seems to me that K&R guarantees that globals are initialized to zero,
> >> not to a nil pointer.  A lot of code will bite the dust given a machine
> >> with a non-zero nil pointer.
> >>
> >> -- Jim Balter, INTERACTIVE Systems (ima!jim)
> >
> >BUT that still doesn't make it legal to 0-> something.
> >
> >-Ron
> 
> I just love those non-sequiturs.  In case you hadn't noticed, *this*
> discussion is about whether NULL can be non-zero.
> 
The reason it appeared to be non-sequitur was because you left out the
rest of the context.  Your comment was a direct reply to another letter
and the topic of conversation was can I use &0->element to find out the
byte offset of element in the structure.

FOO.