On Tue, 14 Dec 1999, John Keiser wrote:
> >From: Vojta Filip <[EMAIL PROTECTED]>
> >
> >So, what I need to initialize in Classpath? I do not need call anything
> >like initializeSystemClass and main() I can (or must?) run by
> >MainThread. And what else?
> >
>
> Welcome!
>
> As far as we can tell so far, Classpath has no initialization order
> required, beyond the standard Sun class loading policy. As long as your VM
> calls static initializers on classes when are loaded, everything should
> happen automatically.
I didn't found where first Thread is created. Must I create it explicitly
or do lazy creation in Thread.currentThread() ? Why MainThread do not
extends Thread? (or why is not Runnable?)
>
> There are a few (very few, actually) places where you will need to call back
> into Classpath in order to get something done. When Classpath goes to 1.2
> support, there will be even more places. But right now, there are only a
> few, and those places are documented in our VM Integration Guide.
I think there should be else one call back - String.intern() - whenever
new literal string or String constant is created. (but maybe it must be
only in 1.2 ?? I don't know.)
So with it I have else one problem - when String is loaded <clinit> is
called. And in <clinit> of String is used Hashtable. And Hashtable has in
<clinit> manipulations with String. But String is not comletly initialized
(<clinit> is not done)...
Vojta
