http://bugs.winehq.org/show_bug.cgi?id=29845
--- Comment #13 from Markus Elfring Markus.Elfring@web.de 2012-02-13 01:40:38 CST --- (In reply to comment #12)
A programmer is free to use any identifiers and preprocessor definitions in his/her program as long as the *compiled code* works and doesn't have side effects or security concerns.
The mentioned software development freedom is restricted if you would like to provide source code that is compliant to the (current) C standard. If the source files do not completely adhere to the programming language rules, I find that the trust in the functionality of the corresponding compilation result will be reduced.
There is no point to do that, and backwards compatibility requires to keep that as it is.
I imagine that there are still opportunities to fix rule violations incrementally. How do you think about to introduce additional preprocessor macros?