On Tue, May 15, 2012 at 8:31 PM, David Jeske <[email protected]> wrote:
> On Tue, May 15, 2012 at 11:56 AM, Jonathan S. Shapiro <[email protected]>wrote: > >> Every other use of unsafe code that I have seen exists to correct a >> deficiency of the language design, most commonly in the area of arrays vs. >> vectors or in the area of low-level I/O. There are known strongly-typed >> solutions for both cases. >> > > - Implementing thunks to primitive shared-libraries or kernel calls .... I > much prefer the PInvoke/unsafe model over having to code all of these > things in external unsafe languages. > > OK. That is certainly a good one, though I tend to think of that code as (a) something that should be generated by a language support tool, and therefore (b) part of the runtime.
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
