Comments on: Dealing with NullPointerExceptions http://www.antwerkz.com/dealing-with-nullpointerexceptions/ Thu, 24 Jun 2010 11:18:23 +0000 http://wordpress.org/?v=abc hourly 1 By: Guillermo http://www.antwerkz.com/dealing-with-nullpointerexceptions/comment-page-1/#comment-15657 Guillermo Mon, 02 Feb 2009 16:28:23 +0000 http://www.antwerkz.com/?p=1432#comment-15657 The problem to me (as a seasoned developer) with NPE usually comes from the "new" Java feature of Autoboxing. It is very easy to forget that you are assigning an object (and thus, possibly a null reference) to a primitive value. The problem to me (as a seasoned developer) with NPE usually comes from the “new” Java feature of Autoboxing. It is very easy to forget that you are assigning an object (and thus, possibly a null reference) to a primitive value.

]]> By: jlee http://www.antwerkz.com/dealing-with-nullpointerexceptions/comment-page-1/#comment-15653 jlee Sat, 24 Jan 2009 13:43:03 +0000 http://www.antwerkz.com/?p=1432#comment-15653 I'm not necessarily recommending that style of chaining as ideal (though I tend to use it to a lesser degree here). I'm just trying to highlight one approach to tracking down the NPE. But yeah, too much of that and it gets unreadable for sure. I’m not necessarily recommending that style of chaining as ideal (though I tend to use it to a lesser degree here). I’m just trying to highlight one approach to tracking down the NPE. But yeah, too much of that and it gets unreadable for sure.

]]> By: Kirk http://www.antwerkz.com/dealing-with-nullpointerexceptions/comment-page-1/#comment-15652 Kirk Sat, 24 Jan 2009 09:05:23 +0000 http://www.antwerkz.com/?p=1432#comment-15652 The first problem with this code is that using get this way is evil. The way to avoid this is to delegate the call and not use get. You can calculate the probability of NPE due this coding style by calculating Halsted volumes and dividing that by lines of code. I call this code density. Code densities beyond 20 are an indication of excessive call chaining. Values around 14 seem to be associated with code that is most readable The first problem with this code is that using get this way is evil. The way to avoid this is to delegate the call and not use get.

You can calculate the probability of NPE due this coding style by calculating Halsted volumes and dividing that by lines of code. I call this code density. Code densities beyond 20 are an indication of excessive call chaining. Values around 14 seem to be associated with code that is most readable

]]>