Hi Dave, Wednesday, May 30, 2007, 12:20:48 PM, you wrote: > If there is no need to return a value then I don't do so. However, the > function is going to process something, and surely you should check that the > processing has succeeded or failed? I have exception and error handling dealt with fully in my functions, by which stage the 'return' at the end becomes redundant because the return value doesn't need checking as the error handler has already taken over. However take the following: $result = $this->calculateSomething($value); If 'calculateSomething' has all the error handling it requires built into it, then isn't checking the value of 'result' superfluous to requirements? Yet even so, I still like to return something at the end regardless :) I guess another way to phrase the same question would be where do you shift all of your error handling - inside the function itself, or in the code that calls it (i.e. checking the $result in the example above). Personally I handle it all in the function otherwise I'm duplicating masses of result checking. It isn't a case of wrong/right, just trying to gauge preferences here. Cheers, Rich -- Zend Certified Engineer http://www.corephp.co.uk "Never trust a computer you can't throw out of a window" -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
