On 8/6/22 12:01 AM, Chris Angelico wrote:
On Sat, 6 Aug 2022 at 13:54, Dan Stromberg <drsali...@gmail.com> wrote:
On Fri, Aug 5, 2022 at 12:54 PM Grant Edwards <grant.b.edwa...@gmail.com>
wrote:
In C, this doesn't do what it looks like it's supposed to do.
if (foo)
do_this();
and_this();
then_do_this();
It's been quite a while since I used C, but with the right compiler
flag(s), I think this may be a thing of the past when compiling with gcc:
https://developers.redhat.com/blog/2016/02/26/gcc-6-wmisleading-indentation-vs-goto-fail
Ah yes, because compiler warnings are always viewed and acted upon.
Have you ever watched the compilation of a large open-source project,
done using the project's own build system and therefore the team's
preferred warning settings? It's normal to have such a spew of
warnings that you can't find anything interesting, or to have new
warnings in new versions of GCC be utterly useless for the same
reason.
ChrisA
You make it so you HAVE to fix the warning by adding the option to make
warnings into errors.
This does mean that you need to fix all the warnings that don't actually
mean anything,
Good code shouldn't generate many warnings, either you have warnings
enabled that you don't care about, or your code is doing things you have
told the complier you shouldn't do.
--
Richard Damon
--
https://mail.python.org/mailman/listinfo/python-list
