This is the mail archive of the
mailing list for the Mauve project.
Re: classpath ./ChangeLog ./THANKYOU ./configure.in...
- From: Stephen Crawley <crawley at dstc dot edu dot au>
- To: raif at fl dot net dot au
- Cc: Stephen Crawley <crawley at dstc dot edu dot au>, Brian Jones <cbj at gnu dot org>, classpath at gnu dot org, Mauve <mauve-discuss at sources dot redhat dot com>, crawley at piglet dot dstc dot edu dot au
- Date: Tue, 08 Apr 2003 09:32:11 +1000
- Subject: Re: classpath ./ChangeLog ./THANKYOU ./configure.in...
> > The problem was that the failing test cases' constructors were not
> > declared public. On Kissme, this (correctly IMO) caused the call to
> > 'Class.newInstance' to throw an InstantiationException...
> shouldnt this be an IllegalAccessException? as the docs states this
> exception is thrown "...if the class or its nullary constructor is not
> also, is it legal for a JVM to try altering the accessibility of a
> non-public, but nullary ctor, before bailing out, and then and only
> then throw an InstantiationException?
Good questions. The JDK javadoc is not entirely clear on either of
them. I'll try some experiments with various Sun JDKs