D
dbeavon
Guest
Control-flow is an integral part of the way exceptions work. I agree that you don't throw exceptions for the express purpose of control-flow. It's not supposed to be used as a GOTO statement. And I agree there is an overhead when using exceptions. For example, it costs more than assigning an output parameter or a return result. But since .net is a jitted platform, I think it would take a LARGE number of exceptions before a line-of-business application would start suffering. Normally it is the out-of-process resources, like remote database, that incur the biggest performance penalties in line-of-business apps. The "client-server" protocol in ABL, for example, will bog things down in a big way - which is proportional to number of packets exchanged over the intranet. This vastly exceeds the CPU concerns related to using SEH in a jitted language.
Continue reading...
Continue reading...