This is something I really don't get in the actual C-logic...[...]Yes, a compiler can reduce (a + b) * 0 to just 0. But it's not
required to do so, and (INT_MAX + 1) * 0 still has undefined
behavior. Undefined behavior is determined by the rules of the
abstract machine *without* any adjustments permitted by the as-if
rule.
Using constants that can be determined at compile time is UB here,
despite the '* 0' mathematically indicating an IMO clear semantics,
but using variables is only UB possibly at runtime? And despite all
that the latter might not even get triggered because it's probably
optimized away? - I can't help, this sounds really crude.
Is there any rationale from the _software designer_'s perspective?
Janis
Les messages affichés proviennent d'usenet.