1 Jul 2010 01:42
Re: Fwd: [scala-user] Is scala.util.concurrent.forkjoin JSR166y?
Paul Phillips <paulp <at> improving.org>
2010-06-30 23:42:43 GMT
2010-06-30 23:42:43 GMT
On Thu, May 20, 2010 at 10:26:58AM +0200, Philipp Haller wrote: > The main reason is to upgrade from the previous version of the > fork/join framework that was used to execute actors in Scala 2.7.x. > The new ForkJoinPool has been almost completely rewritten, is actively > maintained, and is much more efficient. However, it requires a 1.6 JVM > because of its use of JVM intrinsics (sun.misc.Unsafe). > > The reason why it is only partially integrated is that we wanted to > include only the classes that we currently depend on. Actually, the > `forkjoin` package was not really meant to be used by clients other > than the standard library. > > > Are there any reasons to use the jsr166y.jar over > > scala.concurrent.forkjoin or vice versa? > > The `jsr166y.jar` is first to receive updates and fixes. However, as > far as I can see, most changes are cosmetic at this point. Important > bug fixes will be integrated into `scala.concurrent.forkjoin` as > quickly as possible of course. According to this ticket, that time has arrived: https://lampsvn.epfl.ch/trac/scala/ticket/3629 Out of curiosity I diffed some files in trunk against the sources I found here: http://gee.cs.oswego.edu/cgi-bin/viewcvs.cgi/jsr166/src/main/java/util/ And the diff is enormous. It's hard to believe it is mostly cosmetic.(Continue reading)
RSS Feed