2 ms·
There is no "correct" behavior here; either one is a valid choice that can be documented and that programs can rely on and exploit. Code doesn't care about whe
by kazinator 3y ago
There is no "correct" behavior here; either one is a valid choice that can be documented and that programs can rely on and exploit.
Code doesn't care about when it's written, only what you run it on, and with what compatibility options.
E.g. one possibility is that ten-year-old code that wrongly assumed the opposite behavior, and has a bug, will start to work correctly on the altered implementation.