[concurrency-interest] Good terminology for setting up effectively immutable objects?

Tim Peierls tim at peierls.net
Mon Apr 28 08:47:37 EDT 2008

I've been griping about the lack of a consensus (let alone a standard) for
this in various places. It's not in JCiP. I think it would be good to
collect ideas, so I added your message to the Java Concurrency wiki and
started a list. Interested parties please add to and comment on the list.



On Mon, Apr 28, 2008 at 6:48 AM, Matthias Ernst <matthias at mernst.org> wrote:

> Hi,
> often I neither want a huge (number of) constructor(s) nor want to
> jump through hoops of using a Builder to guarantee final-ness of my
> object's dependencies but want to rely on effective immutability
> instead. I want to rely on my clients' common sense that anything that
> is not documented as changeable should not be changed during use. I.e.
> a number of setters that they may only call a) before starting to use
> the object and b) before publishing it to other threads.
> Is there a concise term to document this? I don't want to repeat that
> sermon above all over. @SetupMethod?
> Sorry if this can be found in JCIP. I don't have one handy right now.
> Thanks
> Matthias
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at altair.cs.oswego.edu
> http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20080428/4362d42b/attachment.html 

More information about the Concurrency-interest mailing list