In a way it’s still the same with more modern languages. Especially OOP, setting an object to Null is just setting the address pointer to to 0x00000000.
Hence NullPointerException / NullReferenceException or similar, depending on the language.
It’s a macro for zero in C, but they aren’t literally the same thing. If you have a value which is zero, you have a value; if your value is null, then it means that you do not have a value; not even zero.
They could have just as easily made it a macro for 0xFFFF.
Isn’t NULL a macro in C for 0? So doesn’t that mean these items are free?
I’d guess, in context, it’s a floating point price column that hasn’t been set, and the table designer didn’t specify the column to be NOT NULL.
I guess Rust would have solved the problem as well.
In a way it’s still the same with more modern languages. Especially OOP, setting an object to Null is just setting the address pointer to to 0x00000000.
Hence NullPointerException / NullReferenceException or similar, depending on the language.
Null is zero in german - so this must be free, it’s a german shop
It’s a macro for zero in C, but they aren’t literally the same thing. If you have a value which is zero, you have a value; if your value is null, then it means that you do not have a value; not even zero.
They could have just as easily made it a macro for 0xFFFF.