[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Query on stacktrace management logic
From: |
Chris Gray |
Subject: |
Re: Query on stacktrace management logic |
Date: |
Mon, 8 Mar 2004 11:47:41 +0100 |
On Thursday 04 March 2004 23:13, David Holmes wrote:
> > David Holmes wrote:
> > > class Class is the first class that must be initialized [...]
>
> Jeroen Frijters replied:
> > Given the wide variety of VMs that use Classpath, I'd be careful with
> > statements like these. For almost every such assumption there will be a
> > VM for which it isn't true.
>
> I meant in a JLS sense. Before you can initialize any class you must have a
> Class instance. Before you can have an instance of any class the class must
> be initialized. Therefore before you can initialize any class you must have
> initialized class Class.
Oops my bad - I confused initialisation with loading. Then I see that Wonka
actually initialises both ThreadGroup and Thread before Class, but OTOH I
also know that the initialisation of our ThreadGroup and Thread are subject
to special restrictions (because at that moment there is no current Thread,
and no Class instance can be created). So David's statement is probably
pretty close to being true in a practical sense, as well as a JLS sense.
--
Chris Gray /k/ Embedded Java Solutions
Embedded & Mobile Java, OSGi http://www.kiffer.be/k/
address@hidden +32 3 216 0369
RE: Query on stacktrace management logic, Robert Lougher, 2004/03/07
RE: Query on stacktrace management logic, Jeroen Frijters, 2004/03/10
RE: Query on stacktrace management logic, Jeroen Frijters, 2004/03/12