On Jun 14, 2018, at 11:33 , Casey McDermott <supp...@turtlesoft.com> wrote: > > However, simply replacing the C++ throw with a Cocoa exception via > [NSException raise : errString format : errString]; seems to work great. > Apparently it unwinds the call stack and is swallowed in the run loop.
Yes, but do be careful about exceptions thrown off the main thread. In (say) GCD-owned threads, there’s nothing AFAIK to catch exceptions, and as someone already mentioned, NSExceptions can’t successfully cross dylib/framework boundaries. _______________________________________________ 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
