Sorry to join late ... that problem using = instead of == is very common. It gave me fits coming from other languages that used = in both places. (I appreciate smart compilers!) I picked up a habit of putting literals on the left
if ( null == myObj ) if ( 0 == myInt ) if ( "".equals(myString) ) // Never get null pointer exception!
Now if I accidentally type = instead of == I'll get a compiler error. I might have to stare at it for a while to see it, but that's better than a really strange runtime error for sure. [ July 13, 2004: Message edited by: Stan James ]
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi