Generally, pay attention to the conventions followed by the functions you're calling, and use the appropriate means to handle the error states they generate.
So if the function you're calling throws exceptions when things go wrong, then you can catch those exceptions to handle the errors. If it returns null when things go wrong (as is the case for Resources.Load) then you need to test for that instead, and an exception handler won't help (unless you try to dereference the null reference that was returned).
↧
