Fixing the Java Memory Model, Part 2

Submitted By: idean
Rating: (Not rated) (Rate It)
Share: Share By Email By Email

Visit


Description

JSR 133, which has been active for nearly three years, has
recently issued its public recommendation on what to do about
the Java Memory Model (JMM). In part 1 of this series, the
author focused on some of the serious flaws that were found in
the original JMM, which resulted in some surprisingly difficult
semantics for concepts that were supposed to be simple. This
month, he reveals how the semantics of volatile and final will
change under the new JMM, changes that will bring their
semantics in line with most developers' intuition. Some of
these changes are already present in JDK 1.4; others will have
to wait until JDK 1.5.

Comments (0)


Add Your Rating

(Not published)
star
starstar
starstarstar
starstarstarstar
starstarstarstarstar
 

Recent Jobs

Official Programmer's Heaven Blogs
Web Hosting | Browser and Social Games | Gadgets

Popular resources on Programmersheaven.com
Assembly | Basic | C | C# | C++ | Delphi | Flash | Java | JavaScript | Pascal | Perl | PHP | Python | Ruby | Visual Basic
© Copyright 2011 Programmersheaven.com - All rights reserved.
Reproduction in whole or in part, in any form or medium without express written permission is prohibited.
Violators of this policy may be subject to legal action. Please read our Terms Of Use and Privacy Statement for more information.
Operated by CommunityHeaven, a BootstrapLabs company.