Comment by josephcsible
3 years ago
> If it's wrong break on compiler time, not on run time
The number being multiplied isn't known until runtime, so there's not a good way of doing this.
3 years ago
> If it's wrong break on compiler time, not on run time
The number being multiplied isn't known until runtime, so there's not a good way of doing this.
Well, funny that the compiler sees no problem in removing a check (on compile time) of a value that is totally possible to obtain, on runtime
Isn’t the very base issue the program didn’t sanitize the input?
Just blindly accepting user input is universally bad methinks.
We might ask if gcc will feel like keeping the sanitizing checks or it will take them out due to some bout of language lawyering as well...
1 reply →