Re: Crash at iOS App Startup - What Could Have Gone Wrong?
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
- Subject: Re: Crash at iOS App Startup - What Could Have Gone Wrong?
- From: Michael Crawford <email@hidden>
- Date: Tue, 21 Apr 2015 06:39:04 -0700
I expect you are correct, however this project is so old it doesn't
have a storyboard, it has a half-dozen .xibs for each of the iPhone
and iPad.
Checking for nil IBOutlets with assert() is helpful.
Some of my code, I know it worked once but when I look at it now it
doesn't make any sense at all. That would be OK but my plan is to
release my source as Free Software, so that it will demonstrate my
expertise to potential employers.
If the program simply worked but I was going to close the source, that
would be OK.
But if the program works yet my code sucks, no one is going to want to
hire me so I feel compelled to refactor it, and that lead to
catastrophe.
Please do understand that I don't expect you to actually debug my code
from my vague descriptions. I'm just looking for encouraging words as
well as any kind of general principles like my own "use assertions
before using debuggers".
--
Michael David Crawford, Consulting Software Engineer
email@hidden
http://www.warplife.com/mdc/
Available for Software Development in the Portland, Oregon Metropolitan
Area.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden