handling errors !

[cold]

when coding.say that i call function UpdateLog() which must open a file,append to it then close it.
alot of errors could rise(file is not there,unable to write..etc).
which is better,to return a false value and handle the error outside the function UpdateLog(),or to end it right there inside the UpdateLog() function if it couldn't find/update the file?

regards

[NogDog]

Normally I have the function return false, so that the main program can "decide" in each such instance whether or not it is a fatal error which should terminate the script, or if there is an alternate path that should be followed, etc. I may have the function raise a warning via user_error(), which I can then toggle on/off via the error_reporting() function while developing the script in order to help with debugging.

[scross]

Yeah, my functions general return false if they fail or if a function they call fails. Then, when it gets back up to application scope, I call a function which removes all the stuff in the output buffer (see ob_start, ob_flush etc to understand this), outputs the error page with the title and message included and exits the application. I could call this function from anywhere, but I find it more manageable if it is only called from the application scope so it doesn't produce anything I don't expect.

[Weedpacket]

...throw an exception...😉

[NogDog]

Weedpacket wrote:

...throw an exception...😉

Unless you need your code to be PHP4-compatible. :p