Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Just as an example, let’s take a method for getting the App Support directory. What if NSSearchPathForDirectoriesInDomains returns no elements? What if it’s not a directory but a file? What if it couldn’t be created?
My methods are getting cluttered up not just by adding doing the checks but also from constructing the error objects, assigning error codes etc.
You probably are overdoing it. From your example, if that function is returning no elements or a file, then something is seriously wrong, and there’s no way that your application can recover from it. At that point, letting the error cause a crash is the only sensible thing to do.