Thanks for this, yes, I imagined there would be a lot of overhead using this approach, but there’s at least 6 man years of development gone into the C# code and it’s not really viable to rewrite it in Objective-C if it’s even possible.
All the Best Dave > On 14 Jul 2015, at 22:14, Jens Alfke <j...@mooseyard.com> wrote: > > >> On Jul 14, 2015, at 1:04 PM, Dave <d...@looktowindward.com >> <mailto:d...@looktowindward.com>> wrote: >> >> I looked at that, but unless I am mistaken, it allow you to bind Cocoa to C# >> not the other way round? > > At some level those amount to the same thing. The difference is which side > wants to “own” the process — with Xamarin IIRC your app launches into .NET. > With Dubrovnik it sounds like you have a regular Cocoa app that can call into > .NET. > > But either way you’re looking at adding a lot of overhead. To run C# code > you’ll need a CLR runtime and a .NET class library, so both of the > technologies above will link Mono into your app. And the C# objects will have > their own garbage-collected heap; I don’t know how big that starts. It’s > totally do-able, it’s just an order of magnitude more overhead than adding a > couple of Obj-C classes to your app. > > —Jens _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
