[Mono-list] Questions on the Mono roadmap

[Paolo Molaro]

On 01/19/05 Dallman, John wrote:
> > Ugh. Managed C++ should be avoided if you want to port the code:
> > try to restrict its use as much as possible, so when you port you
> > can rewrite the small bit of work.
> 
> We have no choice but to write a whole load of wrapper functions
> in it, but they're being generated rather than hand-written, so 
> changing our generation tool is quite possible. 

Excellent.

> > from assemblies automatically. It can probably be tweaked
> > to suit your needs (like create C++ classes instead of
> > C functions).
> 
> C functions would do fine. 
> 
> > It's not yet clear how to keep it working when we'll have
> > a moving GC, though (in mono 2.0).
> 
> Oops...

Well, the issue is that we need to design a good API for it,
which may involve making MonoObject* a handle to the GC memory
or automatically doing pinning etc. We'll try to figure out a solution
to make the interface as easy to use as possible.

lupus

-- 
-----------------------------------------------------------------
lupus@debian.org                                     debian/rules
lupus@ximian.com                             Monkeys do it better