There is no difference between
char *p = nullptr;
and char *q = 0;
other than the variable name; the two have to compare equal: (p == q).What's wrong with 0 is that when it's not in an expression where it's being converted to integer type, it's just an integer.
volatile int* x=0; x=0x1234;
Did I just deference the null pointer or make a valid write to that memory location? There is no way to know for sure, you can only apply heuristics to make a guess.
Of course if the lines are that closely spaced you can guess, but in real code they can be in different translation units.
If you're using some environment in which x isn't the zero address, but you do want the actual zero address, you need some other way to obtain it, like converting a non-constant expression:
const int x = 0;
char *zeroaddr = (char *) x;
C implementations are not required to diagnose null dereferences. In many familiar environments, its arranged by the way the program is loaded. An unmapped page of virtual memory is put at that address. That scheme can be defeated if an offset is involved ptr[large_offset] or ptr->member where member is at a large offset into the struct type.It's possible to have run-time checks for a null pointer as a compiler option, with a run-time penalty. Other than that, you can use assertions to defend against them.