Re: enabling optimizations (-Og) with --enable-debug

On 01/15/2015 10:47 PM, Ashod Nakashian wrote:
> It probably is, but with some caveats. My main concern would be
> unnecessary code pollution. It's true that these warnings could be
> really useful. They might hint at actual issues in some cases (for
> example an unhandled error in the unused-result case).
> But suppressing them can also muddle the code. I rather 'fix' the cases
> that might hide real issues rather than suppress/silence noise just for
> its own sake.

Our OOo/LO history has shown us that compiler warnings are only helpful 
for development if they break the build.  Unfortunately, that means that 
you occasionally need to find a way to work around a false warning 
unhelpfully emitted by some compiler.