-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
Error Routines
- Thread starter Smee
- Start date
- Similar Threads Similar Threads
You can't find the line directly but if you can put more than one ErrorLevel statement in your Sub vectoring to different labels to more precisely locate where the error occurred. Using B4PObject(6) and the Door library or my http://www.b4x.com/forum/additional-libraries/2305-exceptions-handling-library.html#post12486 you can find out more details of the error. The help for the Exceptions library has a topic on error handling in Basic4pppc.
The default exception handling in an optimised compiled program does not show the error line. For debugging my http://www.b4x.com/forum/additional...-legacy-optimised-applications.html#post27120 includes a DebugRecompiler which can give the error line but you wouldn't use if for the final application because of the performance hit.
You can't resume after an Exception.
The default exception handling in an optimised compiled program does not show the error line. For debugging my http://www.b4x.com/forum/additional...-legacy-optimised-applications.html#post27120 includes a DebugRecompiler which can give the error line but you wouldn't use if for the final application because of the performance hit.
You can't resume after an Exception.
Many thanks for the reply.
i know what will cause the error i am trapping for.
I am currently using a goto as a "resume next" but i wanted it a little more sophisticated in case of another error being triggered
Maybe error level improvements in the wishlist?
Thanks again
i know what will cause the error i am trapping for.
I am currently using a goto as a "resume next" but i wanted it a little more sophisticated in case of another error being triggered
Maybe error level improvements in the wishlist?
Thanks again
Unlikely as Basic4ppc error handling is based upon how .NET handles errors, which is always by non-restartable Exceptions. See that help topic in the Exceptions library.