__has_include__ is problematic

Florian Weimer fweimer@redhat.com
Thu Jan 10 14:21:00 GMT 2019


Can we remove __has_include__?

Its availability results in code which is needlessly non-portable
because for some reason, people write __has_include__ instead of
__has_include.  (I don't think there is any difference.)

Thanks,
Florian



More information about the Gcc mailing list