From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnold@skeeve.com Message-Id: <201210301515.q9UFF8rA006751@freefriends.org> Date: Tue, 30 Oct 2012 09:15:08 -0600 To: 9fans@9fans.net References: <15723310.yIARpoJMSL@coil> <4824335454f1b1d47dbc8439b4af8ea3@kw.quanstro.net> <20121029223541.8C198B827@mail.bitblocks.com> <0f05642b113b3ecfc160e82a9ca4db32@brasstown.quanstro.net> <20121029232652.5160BB827@mail.bitblocks.com> <74f73b64cc6de4a3bd10367591439816@kw.quanstro.net> <20121030003501.AE691B827@mail.bitblocks.com> <20121030030634.1DDFFB827@mail.bitblocks.com> <1d49069b9f4d221474f9ea9bf37c3f58@coraid.com> In-Reply-To: <1d49069b9f4d221474f9ea9bf37c3f58@coraid.com> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [9fans] caveat... optimizer? the `zero and forget' thread on HN Topicbox-Message-UUID: cd5f3f90-ead7-11e9-9d60-3106f5b1d025 > > > gcc etc. are used to deliver a lot of code that is used in > > > real word. And without a standard there would've been lot > > > less interoperability and far more bugs. This remains true. It is possible and not that difficult to write code that can be successfully and correctly compiled by multiple compilers (like, oh, i dunno, maybe, GNU awk :-). > > Most interoperability delivered by gcc comes from the fact that gcc is > > widespread, not that the standard is effective. If it was we wouldn't need > > to port gcc to everything. > > even clang got forced into bug-for-bug compatability mode. Also the Intel compiler, ICC. Like many things, standards seem to obey a bell curve. The problem is that we're on the descending side on so many of them... (Dare I say it? "POSIX". Freel free to run screaming in horror. :-) Having lived through the Unix wars of the late 80s and early 90s, I think that overall standards are a good thing. It just seems that more recently the comittees keep adding stuff in order to justify their continued existence, instead of solving real problems. Arnold