Issues with Exit Sub & Exit Function for Error Handing

[Brandon Parker]

Carl,
     There seems to still be issues with "Exit Sub" and "Exit Function" when setting things up inside Subroutines/Function for Error Handling.

When "Exit Function" is executed LB5 Alpha 351 blows up and the user is forced to either Exit or Continue.

The error message is: "Unhandled exception: Message not understood: #debugName"


When "Exit Sub" is executed LB5 Alpha 351 throws an error and then successfully exits the Subroutine.

The error number and message (separated by a colon) is: "0 : No SUB to EXIT."


Here is the code that produces these issues.
Call testSubroutine 0
Call testSubroutine 2

Print testFunction(0)
Print testFunction(2)
End

Function testFunction(x)
   On Error GoTo [Error]
       testFunction = (1/ x)
       Exit Function
   [Error]
       Print Err;" : ";Err$
End Function

Sub testSubroutine x
   On Error GoTo [Error]
       Print (1/ x)
       Exit Sub
   [Error]
       Print Err;" : ";Err$
End Sub

Hardware:                Samsung Laptop Intel Core i7, 16GB of RAM
Operating System:    Windows 10 Home build 18363.1016 - 64-bit


{:0)

Brandon Parker

[Carl Gundel]

Aug 30, 2020 21:16:21 GMT -5 Brandon Parker said:

Carl,
     There seems to still be issues with "Exit Sub" and "Exit Function" when setting things up inside Subroutines/Function for Error Handling.

When "Exit Function" is executed LB5 Alpha 351 blows up and the user is forced to either Exit or Continue.

The error message is: "Unhandled exception: Message not understood: #debugName"


When "Exit Sub" is executed LB5 Alpha 351 throws an error and then successfully exits the Subroutine.

The error number and message (separated by a colon) is: "0 : No SUB to EXIT."


Here is the code that produces these issues.

Thanks.

[Carl Gundel]

Aug 30, 2020 21:16:21 GMT -5 Brandon Parker said:

Carl,
     There seems to still be issues with "Exit Sub" and "Exit Function" when setting things up inside Subroutines/Function for Error Handling.

When "Exit Function" is executed LB5 Alpha 351 blows up and the user is forced to either Exit or Continue.

The error message is: "Unhandled exception: Message not understood: #debugName"


When "Exit Sub" is executed LB5 Alpha 351 throws an error and then successfully exits the Subroutine.

The error number and message (separated by a colon) is: "0 : No SUB to EXIT."

Okay, I've sorted this for build 352.  Here is the output of the program now:

11 : Can't create a Fraction with a zero denominator
0.5
11 : Can't create a Fraction with a zero denominator
0
0.5

Interestingly the EXIT SUB and EXIT FUNCTION statements were both broken, but for completely different reasons.

Thanks again.

[Brandon Parker]

Awesome...!!

We are all so very excited to see progress on LB5; keep up the great work!


{:0)

Brandon Parker