For completeness, our other alternative is to target the unsafe CLI subset. At that point we can do almost anything we want, but we are completely on our own for implementation of GC and the like. I'm not even sure that there are contracts in that corner of CLI regarding sequence points and JIT-generated temporary values. Even if those contracts exist in the specification, it's likely to be an under-explored part of the JIT subsystem, and one that nobody feels any urgency about addressing. For reference to use a unsafe with a GC you only need to pin / fix it by calling the GC.KeepAlive method. This can also potentially be used for manually managing references from static data that is not Marked . No idea on mono support. Ben
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
