Oh. My. God. It's like using the emergency brake every time you want to slow down.
Yes, there are non-trivial performance issues with try/catch. Not so much that it shouldn't be used for, you know, error-trapping, but... Also, used in this manner, you never know when something unexpected happened vs. intentionally erroring. This guy needs to be LARTed, quickly. That's just lazy and will lead to totally unmanagable code down the road, IMHO. And that's not even thinking about debugging.... Best of luck reprogramming this guy. --Ben Brad Wood wrote: > 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:232341 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=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
