This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [4.4] [C++] separate pedwarns and permissive errors.


On 02/03/2008, Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
>  > * The C++ front end now differentiates between pedantic warnings and
>  > permissive errors. The former are controlled by -pedantic and
>  > -pedantic-errors, while the latter are errors that can be downgraded
>  > to warnings.  As a result, some diagnostics that used to be errors are
>  > now just warnings. Please, refer to the GCC manual for further
>  > information about these options.
>
>
> How can permissive errors be downgraded to warnings?  That is something
>  I'd also add to this description.

Using -fpermissive. Hum, I think my text didn't convey the idea I
wanted to convey. The user-visible changes are that some previous
errors will now be warnings by default. For example, diagnostics about
GNU C++ extensions are now warnings that you can make into errors with
-pedantic-errors. I realise now that talking about "pedantic warnings"
and "permissive errors" is just going to confuse users.

Perhaps this is better?

 * Some of the errors of the C++ front end that could be downgraded to
warnings by using -fpermissive are now warnings by default. They can
be converted into errors by using -pedantic-errors.

Also I would like to mention:

 * C++ front-end errors that can be downgraded to warnings to support
legacy code mention -fpermissive when -fdiagnostics-show-option is
enabled.

Cheers,

Manuel.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]