On Oct 27, 2003, at 2:01 PM, Mark Wielaard wrote:
On Mon, 2003-10-27 at 13:15, Bryce McKinlay wrote:
On Oct 27, 2003, at 1:05 AM, Mark Wielaard wrote:
I suggest to move the System.loadLibrary("javaio") calls completely
into the VMInterface classes. We want to have a system where (at
least
for lan
Hi,
On Mon, 2003-10-27 at 13:15, Bryce McKinlay wrote:
> On Oct 27, 2003, at 1:05 AM, Mark Wielaard wrote:
> > I suggest to move the System.loadLibrary("javaio") calls completely
> > into the VMInterface classes. We want to have a system where (at least
> > for lang, net, io and util) we have the
On Oct 27, 2003, at 1:05 AM, Mark Wielaard wrote:
Hi,
On Sat, 2003-10-25 at 19:43, Dalibor Topic wrote:
One of the things I keep stumbling over whenever I merge code from
Classpath into Kaffe is the different native library names. Would it
be
possible to separate those out into their own VMInter
Hi,
On Sat, 2003-10-25 at 19:43, Dalibor Topic wrote:
> One of the things I keep stumbling over whenever I merge code from
> Classpath into Kaffe is the different native library names. Would it be
> possible to separate those out into their own VMInterface class and use
> references instead?
>
On Oct 26, 2003, at 6:43 AM, Dalibor Topic wrote:
One of the things I keep stumbling over whenever I merge code from
Classpath into Kaffe is the different native library names. Would it
be possible to separate those out into their own VMInterface class and
use references instead?
I'd prefer so
Hi all,
One of the things I keep stumbling over whenever I merge code from
Classpath into Kaffe is the different native library names. Would it be
possible to separate those out into their own VMInterface class and use
references instead?
I'd prefer something like
System.loadLibrary(VMNativeL
6 matches
Mail list logo