[Mono-list] Internal calls

Dan Lewis dihlewis@yahoo.co.uk
Mon, 11 Feb 2002 12:35:53 +0000 (GMT)

> The plan was to develop something like this also to generate the C structures
> from corlib of some objects, like the reflection ones used in
> reflection.h.

That's interesting, I'll have a look at what I can do with that.
> I think only corlib should have internal calls, the other asseblies
> should be mostly independent of the actual runtime, I guess.

This would be nice. But looking at the MS assemblies, some low-level classes
are not in the corlib (System.Net.Sockets springs to mind). So it looks like
it's going to have to be the corlib and a minimal selection of System

> I think the tool is useful (it was already planned), so you can commit
> it in cvs, but I'd wait to deploy it until we have mcs and corlib
> compiling on Linux, since otherwise it may cause build problems
> for some people.

Yeah it's definitely not something to integrate straight away. But I'd like to
just leave it hanging around to see if you guys who are actually writing the
internal calls find it useful. Eventually I guess you'll move the internal call
implementations from metadata to a seperate icall directory, at which point it
becomes useful.

As you say, corlib completion is the probably number one priority at the
moment. Talking of which, is there any list of the critical classes that are
missing for this?


Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts