[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse.org-architecture-council] Please weigh in on these JSRs.
|
+1 to all of those from my side
For JSR I don't like the "try-with-resources statement", esp. given the JSR 335. The rest however looks useful.
Bernd
-----Original Message-----
From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
Sent: Dienstag, 23. November 2010 15:56
To: eclipse.org-architecture-council
Subject: [eclipse.org-architecture-council] Please weigh in on these JSRs.
Hey folks. Please read this one carefully.
You've been asked to comment on several important JSRs before the
Eclipse Foundation votes on them. Please take a look as three of these
JSRs have significant impact on the future of Java (and lambda
expressions sound all Lisp-y and interesting).
JSR 334 - Small Enhancements to the Java Programming Language - JSR
Approval Ballot
Last day to vote: 29 November 2010
URL for JSR: http://jcp.org/en/jsr/detail?id=334
JSR 335 - Lambda Expressions for the Java Programming Language - JSR
Approval Ballot
Last day to vote: 29 November 2010
URL for JSR: http://jcp.org/en/jsr/detail?id=335
JSR 336 - Java SE 7 Release Contents - JSR Approval Ballot
Last day to vote: 29 November 2010
URL for JSR: http://jcp.org/en/jsr/detail?id=336
JSR 337 - Java SE 8 Release Contents - JSR Approval Ballot
Last day to vote: 29 November 2010
URL for JSR: http://jcp.org/en/jsr/detail?id=337
Thanks,
Wayne
--
Wayne Beaton, The Eclipse Foundation
http://www.eclipse.org
--
Join me at EclipseCon 2011
http://eclipsecon.org/
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
