Re: [PATCH 1/3] grep: add --warnings={always,never,auto}.

[Paul Eggert]

On 08/27/2010 03:56 AM, Paolo Bonzini wrote:
> On 08/27/2010 12:13 PM, Jim Meyering wrote:
>>      I have a fundamental aversion to making functionality like this new
>>      warning depend on whether a standard input or output stream is a
>> TTY.
>>      Personally, I want my script to fail if I use a regexp that deserves
>>      a warning.
> 
> Me too, but this would be against POSIX, and I think it is also
> borderline to remove the warning only for POSIXLY_CORRECT.

I don't understand that argument.  Is it saying that because we're
already violating POSIX unless POSIXLY_CORRECT is set,
that means it's OK to violate the GNU coding standards unconditionally?

I'm with Jim here.  Let's disable the warnings if POSIXLY_CORRECT
(because POSIX says so), but leave the warnings in otherwise
(because the GNU coding standards say so).