Re: the actual c9x patch

[Ulrich Drepper <drepper at cygnus dot com>]

Zack Weinberg <zack@rabi.columbia.edu> writes:

> Now, think in terms of the C library. -std=c9x might reasonably be
> expected to cut out POSIX, SVID, etc. from the standard headers.
> -std=gnu might be expected to activate GNU library extensions.

The question must be: when do you want to have an option to use only
the GNU extensions before the introduction of the c9x extensions.
This is the only possibility missing.

With your approach we would get (I leave K&R out):

	-ansi			C89 compliant
	-std=c89 -ansi		same as -ansi
	-std=c89		GNU C without GNU extensions
	-std=c9x -ansi		C9x compliant
	-std=c9x		GNU C including C9x stuff

With the currently implemented gcc behaviour we have:

	-ansi			C89 compliant
	-std=c89		same as -ansi
	-std=c9x		C9x compliant
	-std=gnu		GNU C including C9x stuff	(default)


My point is that me never had a more to select different versions of
GNU C and I don't think this is really necessary.  There is no standard.

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