problems with iso restrict

[Alexandre Oliva]

On Dec  4, 1998, Ulrich Drepper <drepper@cygnus.com> wrote:

> 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 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.

Isn't it possible to make some lexer/parser hack to accept restrict as 
a name, rather than as a keyword, if it is not in a context where
the restrict keyword would not be acceptable, and flag restrict as a
symbol name for the rest of that translation unit or so?

-- 
Alexandre Oliva  http://www.dcc.unicamp.br/~oliva  aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil