RFR 8169435 : ClassLoader.isParallelCapable is final and conflicting method may get VerifyError (original) (raw)

David M. Lloyd david.lloyd at redhat.com
Fri Nov 11 15:03:44 UTC 2016

On 11/11/2016 05:07 AM, Alan Bateman wrote:

On 11/11/2016 10:46, Vladimir Ivanov wrote: Alan,

I've looked through the current thread and also review thread [1] for original change (8165793), but haven't found any discussion why making it static (instead of instance final) is undesirable. Can you shed some light on it? Is it mainly usability concern (loader.isParallelCapable() vs ClassLoader.isParallelCapable(loader))? I assume you mean to address this to Brent rather than me, but yes, an instance method would be nicer (if we can get away with it).

I think the question was "why not?". A static method can never conflict, and doesn't have a usability impact. A final method can always conflict, and a non-final method is always potentially problematic for the multiple reasons already stated on this thread.

By score, static wins. So, why not?

More information about the core-libs-dev mailing list