Here is a weird UV error condition that I just spent way too long debugging:
>CT BP SB
SB
0001 X = ""
0002 IF X EQ "" THEN X = Y
0003 PRINT "ONE"
0004 PRINT "TWO"
0005 PRINT "THREE"
0006 PRINT X
0007 Y = "A"
>RUN BP SB
ONE
TWO
THREE
Program "SB": Line 6, Variable "X" previously undefined. Empty string used.
Why does the run-time error happen in line 6 instead of line 2? This is
_not_ what I was expecting.
In D3:
:run bp sb
[B10] in program "sb", Line 2:
Variable has not been assigned a value; zero used.
ONE
TWO
THREE
0
I like the way D3 reports this better. Is this a normal, known UV thing?
Perhaps this is just the first time I have ever tripped over it...
/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
