zak Member Licensed User Longtime User Aug 7, 2018 #1 I know that in b4a and b4i a try catch error is generated for long subroutines in debug mode. Does the same rule apply for b4j? If so what is the best technique to split it into smaller ones?
I know that in b4a and b4i a try catch error is generated for long subroutines in debug mode. Does the same rule apply for b4j? If so what is the best technique to split it into smaller ones?
MarkusR Well-Known Member Licensed User Longtime User Aug 7, 2018 #2 smaller function/sub more modular or more try catch usage in long sub routines. can you post a example of your long sub routine? https://www.b4x.com/android/forum/threads/unhandled-exceptions.77506/ Last edited: Aug 7, 2018 Upvote 0
smaller function/sub more modular or more try catch usage in long sub routines. can you post a example of your long sub routine? https://www.b4x.com/android/forum/threads/unhandled-exceptions.77506/
Erel B4X founder Staff member Licensed User Longtime User Aug 8, 2018 #3 zak said: I know that in b4a and b4i a try catch error is generated for long subroutines in debug mode. Does the same rule apply for b4j? If so what is the best technique to split it into smaller ones? Click to expand... What is the problem that you are trying to solve? Upvote 0
zak said: I know that in b4a and b4i a try catch error is generated for long subroutines in debug mode. Does the same rule apply for b4j? If so what is the best technique to split it into smaller ones? Click to expand... What is the problem that you are trying to solve?
