[Mono-devel-list] Overcoming PInvoke limitations in e.g. Mono.Posix

[Sebastien Pouliot]

>> Three solutions.  One: generate only the fields which can be assumed to
be
>> there (bail out if they aren't).  Two: generate all fields, and have
programs
>> check explicitly (through reflection) that they exist.
>
>Yuck.  *Requiring* Reflection to use your structures is broken.
>Especially if we want to implement CAS (Code Access Security) at some
>point

Actually it's being implemented right now ;-)

> and allow access to Mono.Posix.  Reflection requires a CAS
>permission to be used.

True, but so is using unmanaged code (not that I like the idea of requiring
reflection in Mono.Posix ;-).

m2c

Sebastien Pouliot
home: spouliot at videotron.ca
blog: http://pages.infinit.net/ctech/poupou.html