On Thu, Aug 27, 2009 at 9:46 AM, Squ Aire<squ...@live.com> wrote: > However, do you have any idea how to accomplish what I actually want to do? > Is my original idea of forcing asserts to crash maybe bad, which is why noone > even thought of suggesting a way to do it?
It's a bad idea. Assertions should be optimized out of your release build. Making assertions visible crashes to your users discourages you from writing assertions and discourages users who have to deal with crashes. If they are debug-only issues, you can safely write tons of assertions and only deal with those that have user-visible effects. This is what we do with OBASSERT and friends (in OmniBase.framework, part of the OmniSource library found at http://www.omnigroup.com/developer/ ). --Kyle Sluder _______________________________________________ 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
