Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.c    |    Meh, in C you gotta define EVERYTHING    |    243,242 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 242,751 of 243,242    |
|    Lawrence =?iso-8859-13?q?D=FFOlivei to Andrey Tarasevich    |
|    Re: NULL dereference in embedded [was: O    |
|    04 Jan 26 02:19:50    |
      From: ldo@nz.invalid              On Sat, 3 Jan 2026 17:24:54 -0800, Andrey Tarasevich wrote:              > The compiler on that embedded system is, of course, aware of the       > fact that address 0x00000000 is perfectly valid and should be left       > accessible. So, for that reason, the compiler is supposed to choose       > some other physical representation for null pointers ...              What if the entire machine address space is valid? Are C pointer types       supposed to add an extra “invalid” value on top of that?              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca