Hi to All
maybe this is a silly or weird question. When an App grows, it may reach a limit, either relatively to code size or to memory engagement. Moreover, when it is rather complex, unexpected exceptions may happen in many parts. I am nor used to rely on Exception management, and i normally work with the so called "defensive programming". Now I have an App with hundreds of subs, potentially giving many kinds of problems, and I am tempted to put a try/catch block in many of the subs, letting the system to catch the "bad surprises". But there is no free cheese, normally. So the question is: may the Try/catch mechanims be implemented without great impact on code performance and memory issues? (BTW,In the past, I did an experiment to put a lot of code inside a try/catch bock and the compiler simply refused to do its work. But maybe I did a wrong analysis of the situation, at that time) Hope I explained my doubts.
maybe this is a silly or weird question. When an App grows, it may reach a limit, either relatively to code size or to memory engagement. Moreover, when it is rather complex, unexpected exceptions may happen in many parts. I am nor used to rely on Exception management, and i normally work with the so called "defensive programming". Now I have an App with hundreds of subs, potentially giving many kinds of problems, and I am tempted to put a try/catch block in many of the subs, letting the system to catch the "bad surprises". But there is no free cheese, normally. So the question is: may the Try/catch mechanims be implemented without great impact on code performance and memory issues? (BTW,In the past, I did an experiment to put a lot of code inside a try/catch bock and the compiler simply refused to do its work. But maybe I did a wrong analysis of the situation, at that time) Hope I explained my doubts.