Re: RFR(m): 8145468u1 deprecations for java.lang

> On Apr 18, 2016, at 3:30 PM, Stuart Marks wrote: > > On 4/17/16 7:06 AM, Dave Brosius wrote: >> Along these lines, is there a reason not to deprecate the >> >> String(String s) >> >> constructor? Now that substring doesn't glom off the original string, i see >> no

Re: RFR(m): 8145468u1 deprecations for java.lang

On 4/17/16 7:06 AM, Dave Brosius wrote: Along these lines, is there a reason not to deprecate the String(String s) constructor? Now that substring doesn't glom off the original string, i see no reason for this constructor. It's a fair point. But I think that historically there's been much

Re: RFR(m): 8145468u1 deprecations for java.lang

Greetings, Along these lines, is there a reason not to deprecate the String(String s) constructor? Now that substring doesn't glom off the original string, i see no reason for this constructor. -dave On 04/15/2016 06:36 PM, Stuart Marks wrote: Hi all, Here's a small update to the jdk

RFR(m): 8145468u1 deprecations for java.lang

Hi all, Here's a small update to the jdk repo webrev for this change. There are no changes to any API deprecations or other specification changes. The changes are confined to the warnings cleanup work. http://cr.openjdk.java.net/~smarks/reviews/8145468/webrev.1.jdk/ The files changed