Review request - 7177315: SimpleDateFormat parses wrong 2-digit year if input contains spaces

2013-06-05 Thread Masayoshi Okutsu
Hello, This is a review request for the fix of 7177315: SimpleDateFormat parses wrong 2-digit year if input contains spaces http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7177315 Webrev: http://cr.openjdk.java.net/~okutsu/8/7177315/webrev.00/ Thanks, Masayoshi

Re: 8015880: GenerateBreakIteratorData build warning

2013-06-05 Thread Masayoshi Okutsu
When I noticed the warning, actually I tried the exactly same fix (both equals and hashCode). It was supposed to generate the same data after the fix, but the fixed one didn't generate identical data. I haven't had time to look into it further. Yesterday Yuka looked into the fixed tool and con

Re: 8015880: GenerateBreakIteratorData build warning

2013-06-05 Thread Naoto Sato
I'd compare the generated break iterator data binary before and after the fix to make sure it is not affecting the compatibility. Naoto On 6/5/13 1:27 PM, Alan Bateman wrote: On 05/06/2013 18:47, Naoto Sato wrote: What about the regression risk? With this fix, the equality would differ from t

Re: 8015880: GenerateBreakIteratorData build warning

2013-06-05 Thread Alan Bateman
On 05/06/2013 18:47, Naoto Sato wrote: What about the regression risk? With this fix, the equality would differ from the prior releases. Would that be ignorable? Naoto This is the tool used in the build, it's the generated data files are that included in the runtime. I've run the regression te

Re: 8015880: GenerateBreakIteratorData build warning

2013-06-05 Thread Naoto Sato
What about the regression risk? With this fix, the equality would differ from the prior releases. Would that be ignorable? Naoto On 6/5/13 12:23 AM, Yuka Kamiya wrote: Hi Alan, Thank you for taking care of this. I investigated how the method had been used. Your fix looks okay. It is not only

Re: 8015880: GenerateBreakIteratorData build warning

2013-06-05 Thread Yuka Kamiya
Hi Alan, Thank you for taking care of this. I investigated how the method had been used. Your fix looks okay. It is not only safe but improves the generator's behavior. I think that we were just lucky that the method had merely wasted CPU and didn't cause a worse problem Thanks, -- Yuka