Re: ThreadPoolExecutor backport

On 31.07.2008 15:19, Lew wrote:
Philipp wrote:

Btw, AFAIK the implementation you are using preceded Java 5 so it is not a backport.

Q2: Does it make a difference if you are in the 1.4 or java [sic] 5
memory model?

Yes, but not to this snippet.

Are you sure with regard to "volatile"? I faintly remember articles about the flaws of the Java memory model before Java 5 and I believe volatile handling was one of them. Or am I mixing up something?

Kind regards

robert
.

Relevant Pages

  • Re: How to use power of Dual/ Quad core Processors in Applet?
    ... synchronization (which also handles memory synchronization between ... Java has a well-defined memory model that the JVM on any system must follow. ... Why would you expect "a lot of Java code to fail due to lack of proper synchronization" in greater proportion on multi-core systems than on single-core systems, given that both have to follow the Java Memory Model? ...
    (comp.lang.java.programmer)
  • Re: Compiling 5.0 syntax java files
    ... Less well known but arguably more important were the addition of the java.util.concurrent and related packages, and the cleanup of the so-called "memory model" for multi-threaded programs. ... The memory model in Java 1.4 and prior had some subtle issues that tended to show up more frequently in multi-processor architectures. ... it is not entirely unreasonable to maintain a Java 1.3 platform. ... If you aren't encountering weird concurrency bugs and your productivity is acceptable, it's understandable the boss is reticent to make a change. ...
    (comp.lang.java.programmer)
  • Re: Compiling 5.0 syntax java files
    ... Less well known but arguably more important were the addition of the java.util.concurrent and related packages, and the cleanup of the so-called "memory model" for multi-threaded programs. ... The memory model in Java 1.4 and prior had some subtle issues that tended to show up more frequently in multi-processor architectures. ... it is not entirely unreasonable to maintain a Java 1.3 platform. ... If you aren't encountering weird concurrency bugs and your productivity is acceptable, it's understandable the boss is reticent to make a change. ...
    (comp.lang.java.programmer)
  • Re: ThreadPoolExecutor backport
    ... AFAIK the implementation you are using preceded Java 5 so it is not ... a backport. ... but not to this snippet. ... about the flaws of the Java memory model before Java 5 and I believe ...
    (comp.lang.java.programmer)
  • Re: ThreadPoolExecutor backport
    ... AFAIK the implementation you are using preceded Java 5 so it is not ... Are you sure with regard to "volatile"? ... about the flaws of the Java memory model before Java 5 and I believe ... difference is, as stated, not relevant to the snippet. ...
    (comp.lang.java.programmer)