>Now, that's not accurate either. "NUL" is simply a normalized form of "null", >because all the ASCII special characters have three upper-case letter names. >There is no doubt that the ASCII guys meant "null" by this. All other matters aside, kindly consider this simple one: If ever you thought homophones were bad, imagine then how to rely upon nothing more than mere case distinction, an ancillary artifact of our system of writing, in two distinct terms whose usages are not radically different from each other but whose meanings most certainly are, is an endeavour virtually guaranteed to be frequently misheard and thus misconstrued when those terms are used in spoken discourse--as they inevitably shall be. --tom
- Re: RFC 263 (v1) Add null() keyword and fundamen... Tom Christiansen
- Re: RFC 263 (v1) Add null() keyword and fundamental data ... Eric Roode
- Re: RFC 263 (v1) Add null() keyword and fundamental ... Tom Christiansen
- Re: RFC 263 (v1) Add null() keyword and fundamen... Russ Allbery
- Re: RFC 263 (v1) Add null() keyword and fundamen... John Porter
- Re: RFC 263 (v1) Add null() keyword and fundamental ... Glenn Linderman
- Re: RFC 263 (v1) Add null() keyword and fundamental data ... Glenn Linderman
- Re: RFC 263 (v1) Add null() keyword and fundamental ... Buddha Buck
- Re: RFC 263 (v1) Add null() keyword and fundamen... Glenn Linderman
- Re: RFC 263 (v1) Add null() keyword and fundamental data ... John Porter
- Re: RFC 263 (v1) Add null() keyword and fundamental ... Tom Christiansen
- Re: RFC 263 (v1) Add null() keyword and fundamental data ... Tom Christiansen
- RE: RFC 263 (v1) Add null() keyword and fundamental data ... David Grove