-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 24 April 2004 22:12, Archie Cobbs wrote:
So applying this logic, there should be no VMFile class because the
native methods of File.java are all implementable in a normal
Classpath-supplied shared library and are not VM-specific.
Just
Am Sonntag, 25. April 2004 11:06 schrieb Thomas Zander:
On Saturday 24 April 2004 22:12, Archie Cobbs wrote:
So applying this logic, there should be no VMFile class because the
native methods of File.java are all implementable in a normal
Classpath-supplied shared library and are not
And if your VM is sufficiently weird
enough (Jikes RVM with m-n threading), then you might actually want to
do something different about files. We used to have our own version
of FileDescriptor and do non-blocking I/O with hooks back into our threading
layer instead of using the default classpath
Am Sonntag, 25. April 2004 13:40 schrieb David P Grove:
And if your VM is sufficiently weird enough (Jikes RVM with m-n
threading), then you might actually want to do something different
about files. We used to have our own version of FileDescriptor and
do non-blocking I/O with hooks back
David P Grove wrote:
On VMFoo vs. NativeFoo vs. PlatformFoo, I really don't care. I only
observe that one person's VMFoo is another person's native/platfrom so
perhaps it makes sense to just pick one name (VM) and leave it. I suspect
you are unlikely to be able to nicely divide the
David P. Grove wrote:
And if your VM is sufficiently weird enough (Jikes RVM with m-n
threading), then you might actually want to do something
different about files. We used to have our own version of
FileDescriptor and do non-blocking I/O with hooks back into our
threading layer instead of
6 matches
Mail list logo
