> On Nov 14, 2015, at 7:01 AM, David M. Lloyd wrote:
>
> On 11/13/2015 06:07 PM, Brian Goetz wrote:
>>> I considered Optional>. I believe it is rare to have a JNI
>>> attached thread calling StackWalker::getCallerClass from native. Most
>>> common cases will find a caller class. Returning an
Hi Max,
On 11/13/2015 10:22 PM, Wang Weijun wrote:
On 2015年11月13日, at 下午9:44, Roger Riggs wrote:
Hi Max,
It would be cleaner to create and use a PrintStream to send the bytes
to the process. We don't want to encourage the poor practice of using
getBytes().
Like this?
http://cr.openjdk.
Hi Joe,
Looks OK.
Best
Lance
On Nov 13, 2015, at 6:15 PM, huizhe wang wrote:
> Additional fix:
>
> Fixed all warnings in the group:
>
> [cast] redundant cast to char in REUtil, RangeToken and Token
>
> fallthrough in RegularExpression, RegexParser
>
> [rawtypes] in RegexParser
>
> Thanks,
Hi,
postponed this, for a later try.
I created 3 subtasks:
https://bugs.openjdk.java.net/browse/JDK-8143008(jaxp)
https://bugs.openjdk.java.net/browse/JDK-8143009(jaxws)
https://bugs.openjdk.java.net/browse/JDK-8143010(corba)
and documented my patches and linked the related discussio
On 12/11/15 13:23, Paul Sandoz wrote:
> Beyond the JDK and 166 are there any more usages out there in the
> wild?
It's not much used because most developers aren't even aware of the
problem it attempts to ameliorate. But new systems are becoming
available with many cores and developers are going
On 11/13/2015 06:07 PM, Brian Goetz wrote:
I considered Optional>. I believe it is rare to have a JNI
attached thread calling StackWalker::getCallerClass from native. Most
common cases will find a caller class. Returning an Optional will
force most common uses to handle the case if it’s absent
