[Mono-devel-list] Native code in mcs & Mono.Posix
Miguel de Icaza
miguel at ximian.com
Thu Jan 8 10:59:02 EST 2004
> On Wed, 2004-01-07 at 22:17, Miguel de Icaza wrote:
> > The reason for the code to live in mcs, is that the C code that is
> > compiled needs to know about the values defined in the C# world. So the
> > solution is to use a C# program with attributes, and from this we
> > generate the C code that gets compiled.
> Does anything in the MCS module actually use Mono.Posix? If it were
> possible, I think it would make sense to move Mono.Posix into its own
> module and write a quick configure script for it. The gdiplus code, on
> the other hand, is not generated from C# land, so it could go into the
> mono/ module perhaps.
Not Mono, but other people do. To establish Unix-based transport
sockets instead of the IP end points that Microsoft supports.
Also, typically applications end up pinvoking Chown/chmod/etc on their
own, so it made sense to provide this functionality there.
I do not want to move the cairo code to mono, because it adds too many
dependencies there, and today we are treating cairo/System.Drawing as an
optional feature (it is not working stably anyways, and is being
More information about the Mono-devel-list