hg: jdk7/tl/jdk: 7012003: diamond conversion for ssl

Changeset: d61d9bf190f5 Author:smarks Date: 2011-01-14 15:31 -0800 URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/d61d9bf190f5 7012003: diamond conversion for ssl Reviewed-by: wetmore ! src/share/classes/sun/security/ssl/CipherSuite.java ! src/share/classes/sun/security/ssl/Cipher

hg: jdk7/tl/jdk: 7010903: impl. of http.maxConnections is different from the description in JavaSE document

Changeset: 983364897f72 Author:chegar Date: 2011-01-14 22:34 + URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/983364897f72 7010903: impl. of http.maxConnections is different from the description in JavaSE document Reviewed-by: alanb, michaelm ! src/share/classes/sun/net/www/h

hg: jdk7/tl/langtools: 7011272: langtools build.xml should provide a patch target

Changeset: 19f9b6548c70 Author:ksrini Date: 2011-01-14 13:59 -0800 URL: http://hg.openjdk.java.net/jdk7/tl/langtools/rev/19f9b6548c70 7011272: langtools build.xml should provide a patch target Reviewed-by: jonathan, jjh ! make/build.xml

Re: Objects.nonNull()

On 14/01/2011 11:30, Stephen Colebourne wrote: These are prior art that users are familiar with, just as much as the JDK. There is actually prior art in JSRs. JSR 305: Annotations for Software Defect Detection Used @Nonnull. In normal circumstances, we would expect this annotation and the

hg: jdk7/tl/langtools: 6571165: Minor doc bugs in JavaCompiler.java

Changeset: 0a509c765657 Author:jjg Date: 2011-01-14 11:55 -0800 URL: http://hg.openjdk.java.net/jdk7/tl/langtools/rev/0a509c765657 6571165: Minor doc bugs in JavaCompiler.java Reviewed-by: mcimadamore ! src/share/classes/javax/tools/JavaCompiler.java

hg: jdk7/tl/langtools: 6419926: JSR 199: FileObject.toUri() generates URI without schema (Solaris)

Changeset: 7c7c1787fbbe Author:jjg Date: 2011-01-14 11:45 -0800 URL: http://hg.openjdk.java.net/jdk7/tl/langtools/rev/7c7c1787fbbe 6419926: JSR 199: FileObject.toUri() generates URI without schema (Solaris) Reviewed-by: mcimadamore + test/tools/javac/api/T6419926.java

Re: Objects.nonNull()

Am 14.01.2011 12:30, schrieb Stephen Colebourne: 2) Other utilities These are prior art that users are familiar with, just as much as the JDK. Google Guava - Objects: public static T firstNonNull(T first, T second) why not? : public static T firstNonNull(T... values) Commons Lang - Obj

Re: Objects.nonNull()

Am 14.01.2011 10:17, schrieb Alan Bateman: Along the lines of Rémi's first suggestion, then another possible candidate is failIfNull(x). +1 Yes, this sounds better to me than throwIfNull(x). The purpose of this method, if I understand right, is to pull out from behind the potential failing

Re: Objects.nonNull()

And I found the original thread, for reference: http://www.mail-archive.com/core-libs-dev@openjdk.java.net/msg02950.html Stephen On 14 January 2011 11:30, Stephen Colebourne wrote: > There are a number of strands to this thread > > 1) Null useful or not. > There are arguments on both sides here,

Re: Objects.nonNull()

There are a number of strands to this thread 1) Null useful or not. There are arguments on both sides here, and developers are divided. Personally, I use null every single day to use not known or not required, such as in a search request: /** * The set of exchange object identifiers, null to

hg: jdk7/tl/langtools: 3 new changesets

Changeset: 2d5aff89aaa3 Author:mcimadamore Date: 2011-01-14 09:45 + URL: http://hg.openjdk.java.net/jdk7/tl/langtools/rev/2d5aff89aaa3 6992698: JSR 292: remove support for transient syntax in polymorphic signature calls Summary: special syntax to denote indy return type through

Re: Objects.nonNull()

Along the lines of Rémi's first suggestion, then another possible candidate is failIfNull(x). -Alan.