Re: [vmi] Extending the VMI to allow setting a default portlib

Tim Ellison wrote: Geir Magnusson Jr. wrote: Tim Ellison wrote: At present, the Harmony launcher creates and passes an instance of the portlib to the VM as it is being created (via an _org.apache.harmony.vmi.portlib init arg). This is good because allows the launcher to define

Re: [vmi] Extending the VMI to allow setting a default portlib

Geir Magnusson Jr. wrote: Tim Ellison wrote: At present, the Harmony launcher creates and passes an instance of the portlib to the VM as it is being created (via an _org.apache.harmony.vmi.portlib init arg). This is good because allows the launcher to define functions used for memory

Re: [vmi] Extending the VMI to allow setting a default portlib

+1 2006/9/15, Tim Ellison [EMAIL PROTECTED]: Geir Magnusson Jr. wrote: Tim Ellison wrote: At present, the Harmony launcher creates and passes an instance of the portlib to the VM as it is being created (via an _org.apache.harmony.vmi.portlib init arg). This is good because allows the

[vmi] Extending the VMI to allow setting a default portlib

At present, the Harmony launcher creates and passes an instance of the portlib to the VM as it is being created (via an _org.apache.harmony.vmi.portlib init arg). This is good because allows the launcher to define functions used for memory alloc, file IO, etc. early. However, we also need to

Re: [vmi] Extending the VMI to allow setting a default portlib

Tim Ellison wrote: At present, the Harmony launcher creates and passes an instance of the portlib to the VM as it is being created (via an _org.apache.harmony.vmi.portlib init arg). This is good because allows the launcher to define functions used for memory alloc, file IO, etc. early.