On 2023-06-06 15:11, Bruno Haible wrote:
There are at least two problems here:
* A logic that distinguishes two types of environments (e.g. git checkout
vs. tarball) increases the test requirements
We need to support both environments. But the more similar they behave,
Paul Eggert wrote:
> >* Compilations from a git checkout and compilations from a tarball
> > behave the same way.
>
> They can behave differently if the person checking out from git (or
> building from a tarball) has a different environment from the person who
> built the tarball.
On 2023-06-04 11:38, Bruno Haible wrote:
* Evaluating warnings is one possible way to improve the quality of a
package. Alternatively, I could have spent the several days on a more
elaborate fuzzing approach, or on writing more unit tests, or on
improving the valgrind integration etc.
Paul Eggert wrote on 2023-05-27:
> If there are other ways to generate warnings to find bugs that are worth
> the trouble of pacifying GCC, then it'd be helpful to use those ways
> too. But plain 'gcc -Wall' is not one of those ways.
> ...
> I ... update the manywarnings module accordingly. This
