problems with iso restrict

[Ulrich Drepper]

Mark Mitchell <mark@markmitchell.com> writes:

> Right.  I have no idea how Ulrich and crew have set up the various
> -std= options and what the defaults are.  `restrict' should not be
> reserved if flag_isoc9x is not set:

The point is to decide what GNU C is.  Does GNU C include all
extensions of ISO C 89 and ISO C 9x?  I think so and the patch
reflects this.

If you now want to have GNU C not including all ISO C 9x extensions we
will have to exclude the definition.  This is IMO a big mistake since
now GNU C is inferior to ISO C 9x.

If this should not happen there will be a time where we have to bite
the bullet and introduce `restrict'.  The committee made the decision
to violate their namespace rules by defining a symbol in the user
namespace but so be it.  All code sooner or later has to be adapted
for this.  Why not do it sooner and prevent people from now on from
writing code which will be invalid under c9x rules?

-- 
---------------.      drepper at gnu.org  ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com   `------------------------