; the second best time is today".
Thanks,
Oren Ben-Kiki
On Thu, Oct 12, 2017 at 1:14 PM, Jonathan Wakely> * Additional `-W...`
flags are introduced in new gcc/g++ versions, which
> > check for new potential code smells, possibly related to later language
> > standards. That's great (thanks!).
>
> And the most widely useful ones are added to -Wall so yo
On Thu, Oct 12, 2017 at 9:40 PM, Andrew Pinski
> -Wno-unkown-warning has already been handled silently since 4.6.0
> (which was released March 25, 2011):
> https://gcc.gnu.org/onlinedocs/gcc-4.6.0/gcc/Warning-Options.html
>
> When an unrecognized warning option is requested (e.g.,
> -Wunknown-war
On Thu, Oct 12, 2017 at 10:10 PM, Jonathan Wakely
wrote:
> > "Most" != "All".
> >
> > IMVHO it is too strong to say "you don't need to know about [other
> ones]".
>
> I didn't say that. I said you don't need to know about the -Wall ones,
> because you get them anyway.
>
Ah, sorry, I misunderstoo
On Fri, Oct 13, 2017 at 4:47 AM, Martin Sebor wrote:
> My organization was particularly focused on warnings so I'm quite
> familiar with the challenges you're hoping to overcome.
I figured I wasn't the only one :-) But it is good to hear from others.
> My
> best advice is to either write a sc
On Fri, Oct 13, 2017 at 10:04 PM, Eric Gallager
wrote:
> If you use autoconf to generate a configure script for your project, I
> recommend using the macros from gnulib's manywarnings.m4 and related
> files:
>
> https://www.gnu.org/software/gnulib/manual/html_node/
> warnings.html#warnings
> http
