Hi Miklos,
>> I only hope that 'others' will get rid of 'their' warnings too ;-)
> Several of us build with --enable-werror, so yes, we fix the warnings
> introduced by others as well. But it's good if you can get rid of them before
> you push. :-)
Of course I will try to fix warnings if I enc
Hi Winfried,
On Fri, Jan 31, 2014 at 11:00:34AM +0100, Winfried Donkers
wrote:
> Thank you, will do so.
> I only hope that 'others' will get rid of 'their' warnings too ;-)
Several of us build with --enable-werror, so yes, we fix the warnings
introduced by others as well. But it's good if you c
Hi Miklos,
>Just use:
>./autogen.sh --enable-werror
>and then any warning from your compiler will fail your build, making sure you
>don't introduce new warnings without noticing them.
Thank you, will do so.
I only hope that 'others' will get rid of 'their' warnings too ;-)
Winfried
_
Hi Winfried,
On Fri, Jan 31, 2014 at 08:12:54AM +0100, Winfried Donkers
wrote:
> Did you find a situation where fLastPos would be without valid value, or is
> just to get rid of the warning?
> In the latter case, how do you find this warning in the long, long list of
> make output? If I know h
Hi Eike,
Just out of interest:
your commit
http://cgit.freedesktop.org/libreoffice/core/commit/?id=d39525f1cfef7a01e45adc9ce5e6e8ebba4250c5
init 'fLastPos' [-Werror=maybe-uninitialized], fdo#73146 follow-up
Did you find a situation where fLastPos would be without valid value, or is
just to get r
