Re: GCC 2.95.2: Bugs in commandline options for C9X

["Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>]

> For example, imagine a standard C library that is distributed as a
> separate product, not in sync with any compiler.  In that case, if the
> library maintainers want to upgrade it to be compliant with C99, they
> must use `restrict' in the headers supplied with the library.

Yes, it is true - autoconf would not help here.

> Does GCC offer any solutions for these kinds of problems?  If not, I
> think it should.

For the specific case of restrict, you *should* be able to check for
__STDC_VERSION__ only. Since gcc does not implement C99 yet, this
symbol does not have a value of 199901. You can use __GNUC__ and
__GNUC_MINOR__ as Claus proposed even without __STDC_VERSION__.

If you need anything beyond that, you should say what it is (not
necessarily on gcc-bugs, though). Perhaps better, you could try to
come up with a patch for it.

> Just to clarify: the library I have in mind is distributed in binary
> form, and most its users are not expected to compile it on their
> machines.  So autoconf cannot solve this.

I hope it is also distributed in source form - why should we care
about non-free software, after all? (I'm about 50% serious here)

Regards,
Martin