On Tue, Mar 27, 2007 at 02:23:47PM +0100, Manuel López-Ibáñez wrote: > On 27/03/07, Martin Michlmayr <[EMAIL PROTECTED]> wrote: > >* Manuel López-Ibáñez <[EMAIL PROTECTED]> [2007-03-27 14:08]: > >> C++ preprocessor emits errors by default for nonconformant code, > >> following the C++ frot-end default behaviour. Users can use the > >> -fpermissive option to downgrade these diagnostics from errors to > >> warnings. > > > >s/frot-end/front-end/ > > > >I'm not sure whether "nonconformant code" is specific enough. Apart > >from this, it looks good. > > It comes from the definition of fpermissive in invoke.texi.
Users aren't going to know from this language what has changed. Manuel, since you're the guy who has been studying the warnings lately: which other preprocessor diagnostics, other than "no newline at end of file", are affected by this change? I would suggest language like: Certain nonconformant code detected by the C++ preprocessor, such as "no newline at end of file", that were formerly warnings are now hard errors. Users can use the -fpermissive option to downgrade these diagnostics from errors to warnings. If there are two or three more, the affected diagnostics could be listed as bullet items.
