On Apr 11, 2014, at 2:26 PM, Greg Parker wrote:
> libdispatch has its own catch-and-halt exception handler here. It does not
> allow exceptions to be thrown across its boundaries. The GCD reference says
> "Your application must catch all exceptions before returning from a block
> submitted to
On Apr 11, 2014, at 4:12 PM, Jens Alfke wrote:
> I know the Obj-C religion is that exceptions “normally shouldn’t be caught”,
> but this isn’t exactly a normal situation, it’s unit testing.
It's not a religion and it's not "shouldn't", it's "if an exception has crossed
through code other than y
On Apr 11, 2014, at 2:12 PM, Jens Alfke wrote:
> I’ve got a weird situation where an NSAssertion failure is terminating the
> process with an “uncaught exception” even though there’s an @try block at a
> lower stack frame ready to catch it. Stack is below. The RunTestCase()
> function, down a
I’ve got a weird situation where an NSAssertion failure is terminating the
process with an “uncaught exception” even though there’s an @try block at a
lower stack frame ready to catch it. Stack is below. The RunTestCase()
function, down at frame 20, is calling the unit-test function inside of a
