gback at cs.utah.edu
Mon Feb 7 11:50:25 PST 2000
> Derek L Davies <ddavies at world.std.com> writes:
> > I wonder why the JVMDI call isn't done like this:
> > (*jvmdi)->SetEventHook(jvmdi, &evtFtn);
> They must have decided it was too annoying.
> > so that the benefits of having an interface pointer are realized for
> > JVMDI as they are for JNIEnv and JavaVM? Briefly, the benefits as I
> > understand them are: COM compatibility, C++ compatitbility, lack of
> > dependancy on vendor specific library name, Multiple implementations
> > of an interface, and interface versioning.
> I thought the benfit was that JNIEnv becomes a second return value:
> A jni call produces a new JNIEnv along with either the return value or
> an error condition. But vmdi is different: there is exactly one
> JVMDI_Interface_1, which you can save a pointer to.
Oh, never mind then. I guess if it's a singleton then there's no need
for a 'this' pointer.
More information about the kaffe