[PATCH] Uninitialised variable produced by kconfig_compiler

[David Jarvie]

If signals are defined, kconfig_compiler includes the mSettingsChanged member 
in the generated class, but it doesn't initialise it. Running valgrind shows 
an uninitialised mSettingsChanged variable being used in the tests in 
usrWriteConfig(). The attached patch fixes this. OK to commit?

-- 
David Jarvie.
KAlarm author and maintainer.
http://www.astrojar.org.uk/kalarm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kcc.diff
Type: text/x-patch
Size: 492 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090621/5e0bcabe/attachment.bin>