- (id) init {
NSAssert(NO, @"Making a nameless dog is forbidden.");
return nil;
}
Here's what used to happen (iPhone 4.3 simulator) when I hit that assert:
2011-10-24 15:43:37.626 p262namedDog[3505:207] *** Assertion failure in -[Dog
init], /path/to/Dog.m:20
2011-10-24 15:43:37.689 p262namedDog[3505:207] *** Terminating app due to
uncaught exception 'NSInternalInconsistencyException', reason: 'Making a
nameless dog is forbidden.'
*** Call stack at first throw:
[etc.]
Here's what happens now (iPhone 5.0 simulator):
2011-10-24 15:47:15.498 p262namedDog[3680:207] *** Assertion failure in -[Dog
init], /path/to/Dog.m:20
That's all! Dude, where's my reason? And without a printing of the reason,
what's the good of the assert? (And hey, I wouldn't mind seeing that lovely
call stack, too.)
This is exactly the same project in exactly the same Xcode; all I did was
switch destination between simulators.
m.
--
matt neuburg, phd = m...@tidbits.com, http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Among the 2007 MacTech Top 25, http://tinyurl.com/2rh4pf
Programming iOS 4! http://www.apeth.net/matt/default.html#iosbook
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
TidBITS, Mac news and reviews since 1990, http://www.tidbits.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
