need for flag for incompatible-changes

[Per Bothner]

Joe Buck <jbuck@Synopsys.COM> writes:
> But there will be problems if you do more than one round of this: first
> -fexperimental-exceptions, then that becomes the standard, and then you
> want to do a new round of experimental exceptions.

You misunderstand.  I am not proposing a flag to control a specific
set of changes.  I am proposing a flag to signal "I am not concerned
about binary compatibility."  It is flag only intended for developers.
Then at each "flag day" (sic) we migrate a whole bunch of changes
from being under control of this flag, to become the default.

> In your case, the change you propose is to add a fourth field to the
> exception table, so ideally the flag should suggest precisely that.

No, that is just *one* of the changes,  though it is one of the more
major and obviously incompatible ones.  I don't want a flag for each
change.

	--Per Bothner
Cygnus Solutions     bothner@cygnus.com     http://www.cygnus.com/~bothner