Re: interned objects

On Fri, Aug 12, 2005 at 11:09:16AM +0100, Matthias Radestock wrote:
> 
> 
> The advantages of this solution is that it is completely orthogonal, and
> relatively easy to implement. The disadvantage is that surprising things
> may happen when the intern status of an object changes over
> time. Problems will also arise when interned objects are mutated. I
> think though that the answer to both of these issues is "just don't do
> that" ;)

Are there any functions for mutating types now?  If not, I'd say this is 
a good solution.  

	Scott



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf