RE: classpath initialization

Joseph, > My problem is that the call stack during initialization of > the System class I looks something like ... > The last line causes an exception, since the static member > properties isn't initialized yet. Initialization is quite tricky. Basically your VMClassloader is making assumptions ab

Fwd: Alan Moore assigns past and future changes

--- Begin Message --- cc - maintainer name: Alan Moore email: [EMAIL PROTECTED] Which files have you changed so far, and which new files have you written so far? changed: RE.java, REException.java, new: MessagesBundle.properties --- End Message --- -- Brian Jones <[EMAIL PROTECTED]>

classpath initialization

Hi I'm trying to use an unmodified classpath (0.06). I already have something working with a modified one. My problem is that the call stack during initialization of the System class I looks something like LOG: called: java/lang/System.()V() LOG: called: java/lang/System.loadLibrary(Ljava/la

Re: OSX port of classpath

> "Chris" == Chris Hoffmann <[EMAIL PROTECTED]> writes: Chris> Any chance these can be folded into classpath 0.07? Probably. Chris> +++ classpath/native/fdlibm/ieeefp.h Fri Oct 3 11:17:44 2003 This part looks fine to me. It might be better to put this check in with the other OS checks