Re: warnings in unit tests

[Bruno Haible]

Jeffrey Walton wrote:
> Apple's port of Clang enables missing prototypes by default. You will
> get the warnings whether you use -Wmissing-prototypes or not. You now
> have to actively disable the warning with -Wno-missing-prototypes.

Thanks for the heads-up. From my perspective, we can treat Apple cc
like MSVC, xlc, Sun cc, clang on Windows, and the other vendor compilers.
Namely, quickly glance over the build log to see whether there are
warnings that look relevant and dangerous, and other than that ignore
the warnings.

This holds for both lib/ and tests/.

Reminder: We never promised a warning-free build, neither of lib/ nor
tests/.

The difference between lib/ and tests/ is that code in lib/ goes into
the binaries delivered by the packages, and therefore if a package
maintainer makes an effort to silence a warning, we will consider
their patch. Whereas for tests, as I said, it is too much
of an effort/cost to do so.

Bruno