This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Don't you think it is reasonable to fix horrible coding errors like this, you are just asking for maintenance problems. In the short term, kludging may make sense, in the long term it sounds a bad idea to keep such non-portable code around.
The problem is that it's portable to every other compiler we've tested. I am curious what icc and xlc do, but those are the only two not tested.
Sorry, I have a different meaning of portable, for me the term is related to the standard, meaning that standard conforming compilers are required to process the code correctly.
"Happens to work on (some/most/all) compilers" is not the same thing at all for me. COmpetent programmers write portable code by knowing what the standard requires, not by trial and error :-)
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |