Skip to main content

After updating to 1.4.0, I noticed that any variable that is not declared or assigned before a subroutine call is marked as an error after that subroutine call.  In the below snippet, line 3 would show as an error in 1.4.0 but does not show as an error in 1.3.3

VAR1 = ""
CALL PROGRAM1(VAR1, VAR2)
CRT VAR2



------------------------------
Robert Metzger
Software Engineer
basys Inc
Baltimore MD US
------------------------------

After updating to 1.4.0, I noticed that any variable that is not declared or assigned before a subroutine call is marked as an error after that subroutine call.  In the below snippet, line 3 would show as an error in 1.4.0 but does not show as an error in 1.3.3

VAR1 = ""
CALL PROGRAM1(VAR1, VAR2)
CRT VAR2



------------------------------
Robert Metzger
Software Engineer
basys Inc
Baltimore MD US
------------------------------

Looks like a possible regression. I started a support ticket to communicate via when I have completed the testing.

------------------------------
Christian Bristow
TSE
Rocket Software Inc
------------------------------

After updating to 1.4.0, I noticed that any variable that is not declared or assigned before a subroutine call is marked as an error after that subroutine call.  In the below snippet, line 3 would show as an error in 1.4.0 but does not show as an error in 1.3.3

VAR1 = ""
CALL PROGRAM1(VAR1, VAR2)
CRT VAR2



------------------------------
Robert Metzger
Software Engineer
basys Inc
Baltimore MD US
------------------------------

Hello everyone

For my part, I find it interesting that rocket-mvbasic reports this variable as 'Referenced undefined variable:' because there is nothing to define if this argument is incoming or outgoing and whether or not it will be assigned by the subroutine.
So, unless I explicitly define this, I prefer to receive this warning.




------------------------------
Manu Fernandes
------------------------------
Hello everyone

For my part, I find it interesting that rocket-mvbasic reports this variable as 'Referenced undefined variable:' because there is nothing to define if this argument is incoming or outgoing and whether or not it will be assigned by the subroutine.
So, unless I explicitly define this, I prefer to receive this warning.




------------------------------
Manu Fernandes
------------------------------
I like the idea of marking this as a warning instead of as an error, so long as it doesn't mark future uses of this variable with an error or warning as well.  Great idea!

------------------------------
Robert Metzger
Software Engineer
basys Inc
Baltimore MD US
------------------------------
Terms & ConditionsAccessibility statement