https://bugs.kde.org/show_bug.cgi?id=387820
--- Comment #3 from Matthew Dawson <matt...@mjdsystems.ca> --- (In reply to Emmanuel Lepage Vallée from comment #2) > kconfigskeleton.cpp is part of KConfigGui, so if the private .h is part of > KConfigGui too, then there's no issue. Nothing from KConfigCore is involved. Sorry, you are correct about that. The name of the class confused me, as I wasn't able to double check that when I replied. As such, I'm generally ok with this plan. My only concern is ensuring that the write happens in a way ensuring that the variables are correctly initialized (through correct acquire/release semantics), but that can be handled in review! If you (or someone else) can write a patch to fix this issue, I'd be happy to review it. Thanks for taking a look into this and LTO! -- You are receiving this mail because: You are watching all bug changes.
