The C standard requires that NULL be defined in locale.h, stddef.h, stdio.h, stdlib.h, string.h, time.h, and wchar.h.
The C++ standard requires that NULL be defined in the c* header corresponding to each of those.
The C standard is very strict about the names a standard can define--each standard header must define precisely the names the standard requires that header to define. The only other names it can define are those that are reserved for the implementation, such as those starting with an underscore followed by another underscore or a capital letter.
The C++ standard is much more permissive in this respect--including any one standard header can have the same effect as including any or all other standard headers.
From a practical viewpoint, C++ implementations used to take quite a bit of advantage of this permissiveness--that is, including one standard header frequently defined the names from a number of other standard headers. More recent implementations tend to work more like the C standard requires, staying much closer to each header defining only the names required by to be defined by that header. They're still probably not as strict about it as the C standard requires, but much closer than they used to be (as a rule).
Answer from Jerry Coffin on Stack OverflowThe C standard requires that NULL be defined in locale.h, stddef.h, stdio.h, stdlib.h, string.h, time.h, and wchar.h.
The C++ standard requires that NULL be defined in the c* header corresponding to each of those.
The C standard is very strict about the names a standard can define--each standard header must define precisely the names the standard requires that header to define. The only other names it can define are those that are reserved for the implementation, such as those starting with an underscore followed by another underscore or a capital letter.
The C++ standard is much more permissive in this respect--including any one standard header can have the same effect as including any or all other standard headers.
From a practical viewpoint, C++ implementations used to take quite a bit of advantage of this permissiveness--that is, including one standard header frequently defined the names from a number of other standard headers. More recent implementations tend to work more like the C standard requires, staying much closer to each header defining only the names required by to be defined by that header. They're still probably not as strict about it as the C standard requires, but much closer than they used to be (as a rule).
C++03 section 18.1.2 says that NULL is defined in cstddef.
On some implementations, iostream may include cstddef, so including iostream would also give you NULL.
Old compilers and NULL
"In which header file NULL macro is defined ? "
Which C standard header file defines NULL character? - Stack Overflow
c - Which windows.h header defines NULL? - Stack Overflow
Hey, so when I was reading my gf's script for C classes, the tutor has written that
In some compilers there is no NULL but it can be easily replaced by a short macro
#define NULL 0
Does any compiler exist, which actually does not recognize NULL?
The NULL macro is defined in <stddef.h>. (It is also defined in several other headers.) It expands to a null pointer constant and is intended to be used with pointers, not with characters.
There is no standard macro for '\0'. It is equivalent to 0 (character constants have int type), and a macro for it would be of limited use.
The character '\0' is often referred to as a null character, but this is different from the NULL pointer constant.
None. And '\0' isn't a char but int. If you don't want to use '\0' you can use 0, 0x0, 00, 000 and so forth...