Hi,
Richard Frith-Macdonald wrote:
On 20 Nov 2011, at 11:38, David Chisnall wrote:
This flag also isn't recognised by clang. What does GCC 4.x need it for?
So the only drawback to removing the option for older compilers is that
non-ascii string literals would malfunction (but such literals have simply been
illegal up to now anyway) ... so it would be reasonable to have an autoconf
check to see if the option works, and disable it and print a warning. I hate
writing autoconf stuff though, so I'd rather someone who's interested in
supporting old compilers did it.
I had a look around the net and found no clear examples on how to check
for compiler features (except the built-in functions). Checking for the
gcc version is in my opinion a bit dirty, since then clang needs to be
separately checked (and maybe somewhen clang will support this option,
etc). Feature checking is always better than version checking.
Any hints about it?
Riccardo
_______________________________________________
Gnustep-dev mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/gnustep-dev
