The one (and only) way of error handling is now 'Try Catch'.
While an error occured, Try jumps to Catch out of the code flow : the code flow ends on the line with the error.
I have so many code to written with database reads and string handles etc etc. At now I must check everything (consist, empty, zero etc etc). Must I write Try Catch for every code line who can probably generate an errror?
Please, if there is a possibility to add a way of error handling that will resume the code flow (like resume next), you will make me very happy.
B4A is great! But for all B4A can, the error handling is too small in me opinion ;-)
While an error occured, Try jumps to Catch out of the code flow : the code flow ends on the line with the error.
I have so many code to written with database reads and string handles etc etc. At now I must check everything (consist, empty, zero etc etc). Must I write Try Catch for every code line who can probably generate an errror?
Please, if there is a possibility to add a way of error handling that will resume the code flow (like resume next), you will make me very happy.
B4A is great! But for all B4A can, the error handling is too small in me opinion ;-)