Yep, on a general level, I like the idea of having support for immutable objects.
In Java, you have to work hard to make objects immutable. Would be nice to make it more automatic, since it should be a high level concept, not a technical detail.
Cheers, =David On Sep 28, 2009, at 3:27 PM, Niclas Hedhman wrote:
I liked this article; http://www.artima.com/articles/hickey_on_time.html And especially when thinking extra hard over mutability of objects and what we can/should do about it. Since we in Qi4j has very exact control over what each class is doing, we could actually force some good practices into place if we think that is a good idea. For instance; * ValueComposite implementations must have final members, and we auto-wrap known mutable types (collections, for instance) with immutable decorators. Discussion on this topic is encouraged. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
