Thanks. I stand corrected. Or rather, I'm still sitting down, trying to take this all in ;-)
I had assumed that constructors effectively synchronized the construction process, but obviously not ... S On 10/10/2007, Will Pugh <[EMAIL PROTECTED]> wrote: > Err. I mean JSR-133. > > --Will > > Will Pugh wrote: > > Look at JSR 166 section 3.5. > > > > > > sebb wrote: > >> On 10/10/2007, Will Pugh (JIRA) <[EMAIL PROTECTED]> wrote: > >> > >>> [ > >>> https://issues.apache.org/jira/browse/CODEC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > >>> ] > >>> > >>> Will Pugh updated CODEC-55: > >>> --------------------------- > >>> > >>> > >> ... > >> > >> > >>> The current problem is that the end of a constructor in no way > >>> guarantees that all threads will see the same values in each field > >>> of an object. > >>> > >> > >> I'm not sure that is correct - for example String is immutable (and > >> threadsafe), yet it has some non-final fields. > >> > >> S/// > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
