Doug Lea also has information here:
http://g.oswego.edu/dl/jmm/cookbook.html
and Intel's doc is here:
http://download.intel.com/design/processor/manuals/253668.pdf
Section 8 has the info on the memory model.
However, as the value is immutable and only set in the constructor, IMO final
is a more accurate description. It can be made volatile later if it actually
becomes mutable.
On Dec 30, 2010, at 12:27 PM, Rainer Jung wrote:
> On 30.12.2010 15:28, sebb wrote:
>> On 29 December 2010 02:17, Filip Hanik - Dev Lists<devli...@hanik.com>
>> wrote:
>>> On 12/28/2010 5:02 PM, sebb wrote:
>>>> On 22 December 2010 16:04, Filip Hanik - Dev Lists<devli...@hanik.com>
>>>>> On 12/21/2010 7:29 PM, sebb wrote:
>>>>>> It would be cheaper to make it final as it's only ever set in the ctor
>>>>>> and is immutable.
>>>>>
>>>>> nothing cheaper, volatile are only expensive to write, not read.
>>>>
>>>> That's not my understanding of how volatile works.
>>>
>>> there is a great book on concurrency that explains how the bus and cpu
>>> architectures handle these, if I remember the title of it, I will send it to
>>> you
>>
>> Please do.
>
> Maybe Filiup meant that one:
>
> Multicore Application Programming: For Windows, Linux, and
> Oracle Solaris (Developer's Library)
> Darryl Gove
> ISBN-10: 0321711378
> ISBN-13: 978-0321711373
>
> At least I recently found some intersting information in there.
>
> Regards,
>
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
