Undefined behavior in C is a reading error
Quoting from the same passage in the standard as the article does:<p>&gt; Permissible undefined behavior ranges from ignoring the situation completely with unpredictable results, to ...<p>Ignoring the situation completely with unpredictable results seems like it covers the current compiler behavior.<p>The author does not like how current compilers work. But his argument against it mixes &quot;it would be better if it worked differently&quot; with &quot;A specific pedantic reading of the standard says they are wrong&quot;. The second kind of argument seems to undercut his wider point. For his wider point is &quot;Compilers should be reasonable rather than turning on pedantry&quot;. At least, that is what I think his point is, and it seems like the much stronger argument to me.<p>Trying to &quot;trip up&quot; the proponents of current behavior by pointing to a possible miss-reading of a comma is not going to do much. Arguing instead that their practice is harmful seems like a much more likely to work approach. That said, such an argument should probably be civil. The article links to this [1] discussion. The link is supposed to show the peculiar arguments used by proponents  of current behavior. What I read there is someone lashing out, calling names, and grand-standing. 
Convincing compilers to be more reasonable is probably going to require a very different tone. Not one of &quot;how dare you be so stupid&quot; but one of &quot;perhaps you could consider this side-effect of current behavior&quot; and &quot;have you considered this approach&quot;.<p>[1] <a href="https:&#x2F;&#x2F;gcc.gnu.org&#x2F;bugzilla&#x2F;show_bug.cgi?id=30475" rel="nofollow">https:&#x2F;&#x2F;gcc.gnu.org&#x2F;bugzilla&#x2F;show_bug.cgi?id=30475</a>