Re:Interviewing programmers: coding test example explained
by avar on Thursday June 03, 2010 @11:24AM
(#1401553)
Actually it's the NULL pointer by definition. 0 is always equivalent to NULL in pointer context, even though you're working with some hypothetical crazy system where NULL is actually #define NULL 1337. It's mandated by the standard.
If (NULL == 0) isn't true you're not using C.
Re:Interviewing programmers: coding test example explained
by cperciva on Thursday June 03, 2010 @03:23PM
(#1402227)
Whoops, I forgot the point I was trying to make. NULL is (void * )(0), but the code
void * p;
memset(&p, 0, sizeof(p));
assert(p == NULL);
isn't necessarily valid, since the binary representation of NULL isn't necessarily as a sequence of zeroes -- even though everybody writes code which assumes that it is.
Re:Interviewing programmers: coding test example explained
by avar on Thursday June 03, 2010 @05:26PM
(#1402627)
Yeah, that's unportable. Although I'm not aware of any system where it
doesn't work.
For the record, regarding 0 in pointer context the C standard has this to say:
An integral constant expression with the value 0, or such an
expression cast to type void * , is called a null pointer constant. If
a null pointer constant is assigned to or compared for equality to a
pointer, the constant is converted to a pointer of that type. Such a
pointer, called a null pointer, is guaranteed to compare unequal to a
pointer to any object or function.
-- C89/C90 section 3.2.2.3 Pointers
The standard then goes on to say that NULL is a macro that's
guaranteed to expand to a null pointer constant.
Re:Interviewing programmers: coding test example explained
by cperciva on Thursday June 03, 2010 @06:10PM
(#1402774)
Yeah, that's unportable. Although I'm not aware of any system where it doesn't work.
Right. I was considering changing this in FreeBSD last year in order to prevent map-at-NULL kernel exploits, but cooler heads prevailed (and pointed out to me how much code such a change would break).
Re:Interviewing programmers: coding test example explained
by nuxi on Friday June 04, 2010 @08:13AM
(#1404066)
Here's the historical list of machines using nonzero null pointers, from comp.lang.c FAQ:
http://linuxdude.com/Steve_Sumit/C-faq/q5.17.html
Re:Interviewing programmers: coding test example explained
by tedunangst on Thursday June 03, 2010 @11:56AM
(#1401659)
The C standard exclusively uses the phrase "null-terminated" to refer to strings.
Re:Interviewing programmers: coding test example explained
by cperciva on Thursday June 03, 2010 @03:15PM
(#1402208)
Huh, you're right. I wonder when they changed that.
Re:Interviewing programmers: coding test example explained
by nuxi on Thursday June 03, 2010 @04:18PM
(#1402403)
They didn't, it's there from at least ANSI C89 (ISO C90):
"A byte with all bits set to 0, called the null character, shall exist in the basic execution character set; it is used to terminate a character string literal."
Re:Interviewing programmers: coding test example explained
by JoachimSchipper on Thursday June 03, 2010 @06:12PM
(#1402777)
I think the rationale is in EBCDIC support; the C standard didn't want to/couldn't mandate ASCII, and therefore could not use the ASCII NUL character.
I honestly don't know whether POSIX/SUS mandates ASCII.
Re:Interviewing programmers: coding test example explained
by nuxi on Friday June 04, 2010 @07:48AM
(#1404032)
As far as I understand, no:
http://www.opengroup.org/onlinepubs/000095399/xrat/xbd_chap0...
Re:Interviewing programmers: coding test example explained
by JoachimSchipper on Friday June 04, 2010 @07:59AM
(#1404040)
I read that as "ASCII must be supported, do whatever else you want". But I don't want to spend too much time on this...
Also, C strings are NUL-terminated, not NULL-terminated. (char)(0) is the NUL character; (void * )(0) is the NULL pointer (usually).