Re: [Yact-dev] Null object

[Daniel B. <ba...@we...>]

On Wed, Apr 12, 2000 at 08:06:56PM -0700, Marius Sundbakken wrote:
> At 09:44 PM 4/12/00 +0200, Daniel Brahneborg wrote:
> >On Mon, Mar 13, 2000 at 08:54:22PM -0800, Marius Sundbakken wrote:
> 
> Gee... my original post is almost one month old... :-)

I wanted to read it carefully. ;)

(This time it only took me two weeks...  I'm getting quicker!)

> >Sometimes null objects are ok though, and when that situation comes up,
> >I'll have no problem introducing YNull(able).  I don't see much use for
> >it right now, though.  Do you (apart from that bug below)?
> 
> Well, again, maybe not so much now, but it fell into my mind and I quickly 
> posted it to the list so that we won't forget :-)

Postings are good, and discussions are good. :)

> But I still stand by it.  Getting rid of those 'if not null' statements 
> makes the code nicer, the flow simpler, and the program more 
> stable.  Stable is the word, not necessarily correct.  But at least stable.

Of course, that's what all the YInputHandler classes are there for.

Interesting...  Previously I've always been the one who has been pushing
for more theoretical solutions, and you're the one holding back.  Now
it's the exact opposite.  Guess you've been studying too much. ;)

I think "use with care" is a good phrase to have in mind, not only for
null pointers.

/Basic