Re: [Cdk-devel] [Bioclipse-devel] Problem with formal charge

[Jonathan A. <jon...@gm...>]

On Tue, Jun 2, 2009 at 5:45 PM, Egon Willighagen <ego...@gm...
> wrote:

> On Tue, Jun 2, 2009 at 5:42 PM, Jonathan Alvarsson
> <jon...@gm...> wrote:
> > On Tue, Jun 2, 2009 at 5:29 PM, Egon Willighagen
> > <ego...@gm...> wrote:
> >> Like with all CDK object fields, NULL is allowed and indicates that
> >> the field is unset, and that the value is undefined.
> >> So, "getFormalCharge() == null" means that the model does not specify
> >> what the formal charge for that atom is.
> >
> > I just must take this opportunity to say: "Don't design to allow null.
> It's
> > a pain to debug." ;)
>
> What alternative are there to indicate that something is unset for an
> 'int' for which any int is a valid value?
>

Huh?? All I am saying is that I hate Null,PointerExceptions so much that I
am open to do almost anything to avoid them.

-- 
// Jonathan