#Xojo try not working code#

#Xojo try not working code#

Tim, I anticipate your reply: “Well, of course when Xojo N+1 comes out you must do a thorough review of ALL your exception handling code, you can’t just expect old code to work in a new IDE!” but this gets back to my (and Kem’s, and others’s) point : using Tim’s coding style, any new Exception added to the language/framework may break existing code. If your “catch only certain exceptions” code is not updated for this new exception, then you are asking for trouble, and you will end up booking seats and not paying for them. If you write code like Tim says (only catching specific exceptions) then you run the following risk: Xojo version N+1 comes out, and Xojo has added a new “FoobarVoodoException” (indicates when the Frangulator has Rebizzled). If anything goes wrong the entire transaction must be rolled back. Sometimes you may find that an exception is a normal part of processing. A classic example would be a transaction that must be atomic, such as “1. That’s your opinion, but there are many situations where the opposite is true.

Just blithely catching all exceptions (but two) and saying “I just don’t care what went wrong” is simply asking for trouble. Overall: It is a little strange at first, but then it becomes very productive, and it pays to learn from the ease of centralized multiplatform code.VB6 was the most productive thing so far, Xojo replaces it with praise, and it is a good escape option for those who have tired of the false promises that have revolved around VB.NET for years.