Re: Re: suggestions for newbee

<snip>

>
> equals is a bit more tricky, because it is more likely to change the 
> behaviour of the program. There are also decisions to make like 
> shallow vs deep comparison (and with deep, there is the use of 
> cycles). So maybe this could be done only explicitely, for instance if 
> the class implements a certain flag interface (ShallowEquals, 
> DeepEquals, ...).

Shouldn't ShallowEquals be "==" and DeepEquals be a.equals(b)?


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click