On Thu, 2018-03-01 at 11:31 +0100, Olivier Mascia wrote:
> When you get used to see, and ignore, tens or hundreds of
> insignificant warnings on each build, it is harder to spot those that
> should trigger real concern.
Hi,
I agree. That's why I keep the projects I work with as much compiler
warning free as possible. Of course, newer compiler brings new
warnings. Some warnings are disable on purpose here (like for
deprecated API, which just hide important warnings), or some warnings
just do not make sense. My past experience with compiler warnings is
that the compiler can be over-pedantic, but it also knows what it
claims about and can help to avoid issues in runtime.
PoDoFo is not my project, I do not do that much cleanup on it myself,
but I did plan to do something about it, I only always forget of it.
Another thing is that the Linux build produces way different set of
warnings from the Windows build, and then there are those 32bit/64bit
builds, for which you sent the patches. I mean, it's sometimes hard to
spot new warnings when it involves multiple architectures, systems and
even compilers (gcc/clang/msvc/...). This is not WebKit, where proposed
patches are automatically built against several environments.
Bye,
zyx
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users
