On Tue, Oct 25, 2005 at 08:22:15PM -0400, Howard Hinnant wrote: > And it is not my assertion that gcc's behavior is better or worse > than other compilers. Only that gcc's behavior is unique in the > industry (I actually haven't tried all other modern compilers) and > that uniqueness in this way is not an asset to gcc.
gcc is "unique in the industry" in any number of ways, as is every other compiler -- in that each of them will have some kind of behavior that is perhaps odd, but might have been accidentally exploited by a programmer who just whacks away at code and accepts anything that happens to compile. I'm still waiting for an explanation as to why this is an important issue, other than that someone has a customer who says that it is. Why is it important to the customer? Why wouldn't a one-line sed script that eliminates the issue altogether suffice?
