KDE/kdevplatform/language/duchain

Andreas Pakulat apaku at gmx.de
Thu Dec 18 07:53:24 UTC 2008


On 17.12.08 22:42:54, David Nolden wrote:
> Am Mittwoch, 17. Dezember 2008 20:47:19 schrieb Matt Rogers:
> > If this assert is there and you're hitting it, then it's something that
> > we need to fix rather than just working around it when KDevelop is compiled
> > in release mode.
> This is a fix.
> 
> The problem: In release-mode there's somewhere a 
> #define Q_ASSERT(X)
> 
> Which means, the code within the assertion is never executed. So the Q_ASSERT 
> should never be around code that has a functionality, like it was in this 
> case.

Right, thats quite normal with Q_ASSERT or the normal C assert.
 
> I'm just asking myself whether we could eventually change this behavior 
> globally for KDevelop(Maybe via CMake), since there is for sure many other 
> affected places.

No we're not going to, having code that does something in an assert is just
wrong.

Andreas

-- 
You are deeply attached to your friends and acquaintances.




More information about the KDevelop-devel mailing list