|
redleader posted:oh yeah, that's right let's take something like arithmetic. sometimes it's faster to let it overflow. sometimes it's faster to treat it as ideal numbers and assume x+1>x. leaving it undefined lets the compiler pick the best option in each individual case, in a way that implementation-defined couldn't effectively detail. and while it would be nice to have a rule that a series of arithmetic statements will eventually resolve to some number instead of formatting your hard drive, it's really hard to write a set of rules that preserve both safety and optimizations
|
#
¿
Jun 29, 2017 23:46
|
|
|
|
| # ¿ May 12, 2024 10:01 |
|
|
TOPS-420 posted:avoiding ub is easy, just follow these 204 simple rules is there a reason they don't get rid of all the ub for trivial things like syntax errors? how did "An unmatched ‘ or ” character is encountered on a logical source line during tokenization (6.4)" survive into this century?
|
|
#
¿
Jul 8, 2017 04:40
|
|