Huge error logs man. You don't want to do that.
There is a built in means of terminating a loop. (break, exit?) Tim > -----Original Message----- > From: Brad Wood [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 15, 2006 12:08 PM > To: CF-Talk > Subject: RE: Try/Catch vs. direct error handling > > While we are talking about try/catch's, does anybody know if > there is a performance hit at all (worth mentioning) when you > use try catch. > > The main reason I ask is because I work with someone who uses > try/catch around EVERYTHING HE EVER CODES. He will even use > it to terminate loops and in place of if statements. > For example, instead of a loop from 1 to arraylen() he would > just until an array out of bounds error was thrown, and then > move on. > Or, instead of an isdefined(), he will try to access the > variable, and then put his <cfelse> in the catch. > I find this over-use to be excessive, but he claims it is > perfectly rational and has no performance implications to > process hundreds and hundreds of try catch's per template. > > Any light you guys can shed? > > Thanks. > > ~Brad > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:232343 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
