Re: [fvwmorg/fvwm] c0ae18: Fix Gcc warnings.

2016-10-22 Thread Thomas Adam
On Sat, Oct 22, 2016 at 11:02:16PM +0100, Dominik Vogt wrote: > On Sat, Oct 22, 2016 at 10:55:39PM +0100, Thomas Adam wrote: > > OK, this looks better. Thanks! > > > > GCC/Clang don't moan at these changes, which is good. The changes built via > > travis-ci just fine. > > > > I say you're good

Re: [fvwmorg/fvwm] c0ae18: Fix Gcc warnings.

2016-10-22 Thread Dominik Vogt
On Sat, Oct 22, 2016 at 10:55:39PM +0100, Thomas Adam wrote: > OK, this looks better. Thanks! > > GCC/Clang don't moan at these changes, which is good. The changes built via > travis-ci just fine. > > I say you're good to merge to master. Good. I think I've also figured out how these safety

Re: [fvwmorg/fvwm] c0ae18: Fix Gcc warnings.

2016-10-22 Thread Thomas Adam
On Sat, Oct 22, 2016 at 10:53:10PM +0100, Dominik Vogt wrote: > Different approach at fixing the warning. Hopefully this one > works without removing any "uninitialised variable" warnings. The > macro SUPPRESS_UNUSED_VAR_WARNING(var) from config.h is used to > remove the "set but not used"

Re: [fvwmorg/fvwm] c0ae18: Fix Gcc warnings.

2016-10-22 Thread Dominik Vogt
Different approach at fixing the warning. Hopefully this one works without removing any "uninitialised variable" warnings. The macro SUPPRESS_UNUSED_VAR_WARNING(var) from config.h is used to remove the "set but not used" warning in the discussed case. I've forced a new version of the branch