quick little CNI question

Sat Apr 1 00:00:00 GMT 2000

> If you don't mind having your code potentially break (because you'll
> be relying on libgcj internals), you can also follow the code sequence
> the compiler uses: call _Jv_LookupInterfaceMethod and treat the result
> as a function pointer.

Has anyone looked at whether the new C++ ABI that is being put together
will remove the need for any sort of lookup?
I seem to recall that one of the recent patches said something about
pure virtual bases not requiring thunks anymore, which IIRC was the
problem with treating
<java>class x extends y implements z { }</java>
as
<c++>class x : public y, public z { }</c++>
(as I understand it, the new C++ ABI would use 
'class x: public y, public virtual z').