Re: monstro-patch: machinery to enable/disable warning/error categories

[Akim Demaille]

>>>>> "adl" == Alexandre Duret-Lutz <address@hidden> writes:

>>>> "Akim" == Akim Demaille <address@hidden> writes:
adl> [...]

Akim> I've not read yet, but what I would most enjoy is:

Akim> 2. -Wall, -Wnone etc. à la Autoconf

adl> Supported.

Akim> 1. support for $WARNINGS 3. exporting the current warnings in
Akim> $WARNINGS to pass them to subtools.

adl> What if I want -Wfoo for one tool and -Wno-foo for the other?

Then you are the kind of users I'm happy not to have to deal with :)

adl> Actually, another question is what should I do so that Automake
adl> use a predefined set of warnings each time it is run?  

Definitely.  E.g., deprecated stuff, or dangerous stuff.  I cannot
imagine there is nothing to warn about.

adl> Currently warning categories can only be selected from the
adl> command line; so how should we do for the rebuild rules?  Add an
adl> AUTOMAKE_AMFLAGS variable just like we have ACLOCAL_AMFLAGS?

Why not?


Back to your point.  I don't think we have to bother with weird cases
(I want to pass -Wfoo to foo but not to bar): such complex cases ought
to be expressed by wrappers.

Still, whatever the suggestion might be (such as adding FOO_WARNINGS
to the GCS in addition to WARNINGS which == *_WARNINGS, or maybe a
structured WARNINGS), it is fundamental to be able to pass a WARNING
to all the applications.

There are *a great many* portability problem we would never have
introduced in our tools if we had WARNINGS=portability,posix support
in Bash, GNU Sed, GNU Awk etc.