Bug #256
Global variables are not initialized when attempt is made to access them inside a procedure, if they weren't touched other than the Global statement.
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
02/26/2020
Due date:
% Done:
0%
Estimated time:
Affected version:
Description
See related issue #152 regarding Help_31.
Previously, the windows would open, but used the wrong background colors.
Now, the first click generates a Software Failure at this command:
Border Rnd(4)+1,P,15-P
Apparently, the reason it fails is that the Global variable P is returning NaN.
This causes a Magician error. If, however, P is accessed before calling the
procedure, it succeeds. (Even attempting to "Print P" before calling will make it work.)
The Global statement itself, should initialize the variable to it's default value if it hasn't already been declared.
Note: Help_31 was mostly working in previous version. Now it causes Software Failure - Magician Meditation.