Kyle Sluder wrote:
On Mon, Sep 28, 2009 at 11:21 AM, James Walker <jam...@frameforge3d.com> wrote:
The drawing seems to work, I'm just curious, and this hasn't happened before
Snow Leopard.
Because of the unified exception model, code that throws and catches
exceptions as a matter of course will trip up the debugger if it's set
to break on exceptions. C++ code uses exceptions as a control-flow
mechanism, whereas Cocoa reserves them for programmer error. There
are a few frameworks (Security is a big one I believe) that are
written in C++ under the hood and make normal C++-ish use of
exceptions.
IOW, breaking on exceptions can lead to this sort of behavior, and
there's nothing you can do about it. :(
I thought the unified exception model was only in 64 bit code? I don't
see what that would have to do with it anyway, since I was trying to
break on C++ exceptions, and did get a C++ exception.
I wonder if Xcode used to have some trickery to hide Apple's C++
exceptions, and show me only my own C++ exceptions, and that got broken?
I guess I should ask on the Xcode list.
--
James W. Walker, Innoventive Software LLC
<http://www.frameforge3d.com/>
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
