jsr166y/openjdk resync
David Holmes
David.Holmes at oracle.com
Thu Aug 12 12:58:06 UTC 2010
Hi Doug,
I could be mistaken but at this stage I don't think new API changes have
any additional overhead. Coordinating the code changes and test changes
is the biggest issue.
David
Doug Lea said the following on 08/12/10 10:24:
>
> A few months ago, we simplified some of the APIs to the ForkJoin
> classes (mainly, removing some methods so as to allow better
> internal automation). The "jsr1yy6" versions of these
> API changes have been in use since then, and we're confident
> that these changes (and corresponding internal implementation
> improvements) should go into the openjdk7 versions.
> In case you are curious, some discussions about them
> can be found in concurrency-interest list archives, including
> http://cs.oswego.edu/pipermail/concurrency-interest/2010-June/007243.html
>
> So we (mainly Martin Buchholz and I) would like to do this.
> Since they involve API changes, I suspect there might be some
> additional process requirements beyond us just doing the
> mercurial commits. If so, can someone let us know what they
> are? We already arranged to have corresponding JCK/TCK tests
> updated.
>
> -Doug
>
More information about the core-libs-dev
mailing list