Re: type based aliasing again

[Richard Stallman <rms at gnu dot org>]

    As was already mentioned here, with slight changes in gcc internals, 
    invalid code will break, sooner or later, but inevitably. And all effort 
    spent to implement your proposal will be in vain.

"Invalid code will break" could mean either "some invalid code will
break from time to time", or "all invalid code will certainly break".
The former is true, but the latter is not.

With my proposal, some of these invalid cases may break in the future.
But chances are most of them never will break.  That is one advantage.

And the ones that do break, will most likely break a year or several
in the future instead of now.  That delay will give more time for
today's current versions of various packages to be replaced with
corrected code.  (The warning would encourage people to make new
versions which don't have these constructs in them.)

Thus, even if a given case does someday break, the resulting user
unhappiness will be less with my proposal.  That is a second
advantage.