Here we go again...

[Roland Krause]

Allright, allright, 
I really thought we were through with this but all the sudden the
crashes because of NULL pointers are back. 

In cleartext: 
If no sources and browsers are open almost any action that leads to a
"Save" related action crashes KDevelop. This is because of unchecked
referencing of pointers that have the real possibility of being NULL. 

I am getting a little bit fed up with this now. There is virtually no
computation time associated with checking these pointers, not even in
projects that have one gazillion files. I see Falks argument that these
functions should not be called but that is effectively not
controllable. See, you have no influence when and by whom a slot will
be called. So, why dont we put an extra little bit of "defensive
programming" in the code and check the fscking pointers. 

I'll be happy to resend the patch for this.
Roland



=====
--
Roland Krause
In the garage of life there are mechanics and 
there are drivers. Mechanics wanted!

__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/?.refer=text

-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«