I wouldn't renounce using try/catch altogether. They are important for object's messaging. They are not merely errors handlers. Exceptions are themselves objects sending a message when a rule is broken. Construct you try/catch hierarchy so that it is extensible. That is, don't catch unless you are at a level of your application to decide logically/graphically wise how to handle the exception.
Mauricio Cuenca wrote: > > What I conclude about this is that is better for my future application to > not have try/catch blocks any at all. Just have the main one in the > bootstrap and let it do the job. > > Am I right or not catching individual exceptions is not a good approach? > -- View this message in context: http://www.nabble.com/Catching-catched-exceptions-tp19874696p19877880.html Sent from the Zend Framework mailing list archive at Nabble.com.
