You're welcome, Charles

Then you will not have any trobules in writing the script. As for the try/catch. Don't use this to often or your code will become x-times bigger (and sometimes slower). Try to use it only when:
- a special action is required for this specific exception, eg. closing connection to the database.
- the original exception should be replaced / wrapped in another, maybe friendlier, exception.

In any other case, no such block is necessary. The generic handler will take care of it. Or your custom handler that will display friendly message and e-mail you on the errors, so you can take care of it.

At least we always deploy our custom error handling, so user will not see filenames and line numbers. However, you don't need it for CLI.