On 27/10/2017 12:02 PM, John Rose wrote:
On Oct 25, 2017, at 11:11 PM, David Holmes <david.hol...@oracle.com
<mailto:david.hol...@oracle.com>> wrote:
Please don't throw IAE that case. I don't want to bikeshed exception
types,
but I think we have a strong precedent for using ICCE when encountering
a questionable classfile configuration (one that shouldn't have come
out of
javac). Note also the ICCE <: VME, so it just gets passed through.
You must have missed Dan's update regarding access checks. He's
already proposed to throw IAE - and I've implemented it. :)
http://cr.openjdk.java.net/~dlsmith/nestmates.html
Actually, IllegalAccessError is not too terrible, although
I'd prefer ICCE for reasons stated.
I read IAE as "IllegalArgumentException", which explains
the warmth of my response. Why did I think you meant
IllegalArgumentException? *That* is unexplainable.
Sorry - it never occurred to me that IAE was an overloaded acronym. :)
David
— John
