VMFile confusion

[Archie Cobbs]

My apologies for adding to the confusion with my question about Etienne's
compliant about adding a VMFile class. Now I understand what he was
saying and agree with him.

To summarize, there is a distinction between native code Classpath
must leave to the individual VM to implement vs. native code that
can be implemented in a shared library which is shared among all
the VMs. Traditionally Classpath has created VMFoo classes only for
native code of the former type.

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.

-Archie

__________________________________________________________________________
Archie Cobbs      *        CTO, Awarix        *      http://www.awarix.com