Re:Subtleties of the ANSI/ISO C standard [pdf]
by abecedarius on Wednesday December 23, 2015 @12:51AM
(#10782180)
The problem with this apology for the standard -- that nobody would interpret it so unreasonably -- is that many programmers (like me) wrote programs assuming what seemed like reasonable bounds on how far compiler writers would go in their language lawyering, which a decade or two later got flouted, making our old code start mysteriously breaking, in a hard-to-figure way, only in the latest versions of the compilers, which at the time were notorious for compiler bugs. If you trust the same compiler writers to respect today's common idea of reasonable engineering tradeoffs, well, I hope it works out better for you.
[ Parent
| on HN ]
Re:Subtleties of the ANSI/ISO C standard [pdf]
by mpweiher on Wednesday December 23, 2015 @05:58AM
(#10782822)
> The problem with this apology for the standard
While I agree with most of what you wrote, it sounds like you are blaming the standard. Seems to me the proper blame is the unreasonableness of the language-lawyering by compiler engineers...which as you point out is a fairly recent phenomenon.
I always like to say that my first C compiler was pre-ANSI-C, so by today's language-lawyering all behavior was undefined and therefore the compiler could have done anything at all. Yet for some strange reason the code produced was more predictable than today.
Re:Subtleties of the ANSI/ISO C standard [pdf]
by to3m on Wednesday December 23, 2015 @08:22AM
(#10783132)