RE: [Ikvm-developers] Welcome

[Jeroen F. <je...@su...>]

lupus wrote:
> If the managed c++ code can be compiled to IL code we should=20
> be able to complete the support in mono to run it.

It can't be. The reason it's in MC++ is because JNI needs to implement a
native interface (abstract C+ class).

> A better solution (since we want to be able to rebuild ikvm in mono as
> well and we're not going to support compiling managed c++ any=20
> time soon) is to write a different jni support assembly for mono. This =

> may require hooks or special handling in the runtime, but I think
> there should be no problem in implementing them if it's not possible
> to implement the assembly with the standard P/Invoke mechanism.

The ikvm JNI provider is pluggable (although the interface hasn't =
stabilised
yet). Whether a fully managed solution will be possible, I don't know. =
It
depends on whether it's possible to create a unmanaged stub for a vararg
function. BTW, even if a fully managed solution is possible, it is =
unlikely
that the same code will work for Windows and Linux, because the JNI =
calling
convention will probably be different between the two platforms.

Regards,
Jeroen