Re: Bugfixes in Scarab are hard

Ronny Voelker wrote:
> 
> Some of the recent commits were fixes for inconsistent data or
> nullPointerExceptions.
> And all of this worked that way, that they ignored the inconsistent data
> or unexpected null-values.
> 

I fully accept your complains. But maybe it was not completely wrong, what i
was thinking when i added the changes. My argumentation in all cases was: 

"It is completely unclear (to me) if this is a matter of inconsistent data,
or inconsistent programming. But from the logic it makes sense to interpret
the occurance of a null as an empty item/list. And if this is principally
allowed at the given place, it could not harm to take care of the NPE. The
true cause would appear at another place sooner or later. Until then a
warning message at this place could be sufficient and the overall behaviour
of the tool would be less rough (to the unknowing users)"

It may have been a wrong and dangerous argumentation though...
So in this sense.. any help to drill down the mentioned problems to 
either irrelevant (because it never occurs), or to the real cause of the NPE
(when it occurs)
is highly appreciated.
-- 
View this message in context: http://www.nabble.com/Bugfixes-in-Scarab-are-hard-tp23740536p23746994.html
Sent from the Scarab - Dev mailing list archive at Nabble.com.

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=455&dsMessageId=2355841

To unsubscribe from this discussion, e-mail: [[email protected]].