[Mono-list] Questions on the Mono roadmap

[Dallman, John]

> >  * [UnmanagedFunctionPointerAttribute( CallingConvention.Cdecl)]
> >    public delegate int TEST_callback_f_t(int a, int b);
> >=20
> > * Marshal.GetDelegateForFunctionPointer(), which creates a
> >   delegate that wraps a pointer to a native code function.
>=20
> These seem relatively simple, and could be implemented. =20

They will be vital for anyone trying to move C#2.0 code that=20
does serious interop.

> Please file a bug report in Bugzilla against these.

Err, I'll try.

> > * Managed C++ ;-)=20
> There is no solution at this point.=20
>=20
> One possibility is to add support for the runtime consumed by the new
> "pure" CLI C++ code, but at this point we have not looked into what it
> would take, nor how complete the support could be.

This wouldn't be pure CLI C++ code. It has to be called from=20
native C code.=20

> My suggestion is to manually wrap the API entry points from=20
> C++ that you need to consume...

The tool for making C wrappers for assemblies that Paolo Molaro=20
mentioned sounds more attractive.=20

> > * Support for calling 64-bit native code, on 64-bit Linux,=20
> >   Solaris, et al.=20
> Mono 1.2 will work at least on two 64-bit platforms: amd64 and Solaris
> 64 bits (Mono 1.1.3 already supports this).

Sounds good, as long as it interoperates with 64-bit native code on =
those.=20

thanks,

--=20
John Dallman