a warning to implement
Gabriel Dos Reis
gdr@codesourcery.com
Wed Feb 6 06:17:00 GMT 2002
Richard Sandiford <rsandifo@redhat.com> writes:
[...]
| > Now you'll have to argue why you're stopping something documented used
| > to work as documented.
|
| My suggestion was to warn only about cases when we can detect the
| behaviour is not documented or well-defined. The option itself could be
| documented that way. If the behaviour of more self-initializers becomes
| defined over time, the number of cases we warn about would go down.
Ah, I think I can live with that. However, someone gave an example of
a GNU package where self-initialization was used. I suppose that your
proposal won't warn about his code. For T = int, I'm still not
convinced although I'm understanding your arguments.
-- Gaby
More information about the Gcc
mailing list