I realize this may be a little off topic for the list, but it's right
on the fuzzy edge of the ObjC language vs the Foundation framework,
and I was hoping our local runtime wrangler expert may have an idea
It appears that exceptions on iOS3.2+ can't be thrown across
NSInvocations. This only seemed to start happening with the iOS3.2
does. This causes a lot of problems for testing frameworks
(GoogleToolbox, OCMock, Hamcrest and most like SenTestingKit) on iOS
as they all depend on throwing exceptions across NSInvocations to
propagate error conditions.
Is this intentional, or a bug? I would think it is a bug, except I
would expect that anyone using any test driven development would've
run into it pretty much immediately. We had seen it internally, but I
hadn't had time to look at the cause until now.
Do not post admin requests to the list. They will be ignored.
Objc-language mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden