Comment by ajkjk 4 years ago Obligatory: it is flabbergasting that this is a quality of language that is still in active use. 5 comments ajkjk Reply Gibbon1 4 years ago It's even more flabbergasting that all these problems haven't been fixed. layer8 4 years ago That would likely break backward compatibility of existing implementation-defined behavior. hyperpape 4 years ago Converting sscanf from undefined to implementation defined behavior would, by definition, not break implementation defined behaviors.There are real cases where removing undefined behavior blocks optimizations, but this doesn't feel like one. 1 reply → hctaw 4 years ago Most of these things can't be fixed at the language level without seriously breakages or preventing users from doing necessarily dangerous things.
Gibbon1 4 years ago It's even more flabbergasting that all these problems haven't been fixed. layer8 4 years ago That would likely break backward compatibility of existing implementation-defined behavior. hyperpape 4 years ago Converting sscanf from undefined to implementation defined behavior would, by definition, not break implementation defined behaviors.There are real cases where removing undefined behavior blocks optimizations, but this doesn't feel like one. 1 reply →
layer8 4 years ago That would likely break backward compatibility of existing implementation-defined behavior. hyperpape 4 years ago Converting sscanf from undefined to implementation defined behavior would, by definition, not break implementation defined behaviors.There are real cases where removing undefined behavior blocks optimizations, but this doesn't feel like one. 1 reply →
hyperpape 4 years ago Converting sscanf from undefined to implementation defined behavior would, by definition, not break implementation defined behaviors.There are real cases where removing undefined behavior blocks optimizations, but this doesn't feel like one. 1 reply →
hctaw 4 years ago Most of these things can't be fixed at the language level without seriously breakages or preventing users from doing necessarily dangerous things.
It's even more flabbergasting that all these problems haven't been fixed.
That would likely break backward compatibility of existing implementation-defined behavior.
Converting sscanf from undefined to implementation defined behavior would, by definition, not break implementation defined behaviors.
There are real cases where removing undefined behavior blocks optimizations, but this doesn't feel like one.
1 reply →
Most of these things can't be fixed at the language level without seriously breakages or preventing users from doing necessarily dangerous things.