Re: [Ql-Users] SMSQ/E and unset variables

On 24 April 2017 at 18:27, Dilwyn Jones wrote: > When SBASIC was first mooted, I remember that there was at the time > discussion that other BASICs gave variables default zero value rather than > stopping with an error - "why couldn't the QL do this?" > > Don't

Re: [Ql-Users] SMSQ/E and unset variables

Hi all, Thanks for your comments. I will look into both XREF and QREF which I have on my system. My latest thoughts are that perhaps we can combine the best of both worlds. We can continue to have default values of zero in the case of locals, while at the same time give an error if no value

Re: [Ql-Users] SMSQ/E and unset variables

Yes, everyone should read "A Brief History". But exactly this case was not bespoken ;-). Ralf Am 24.04.2017 um 18:27 schrieb Dilwyn Jones: When QDOS evaluates an expression and encounters a variable with no value assigned, it STOPs with “error in expression” and reports the line number. The

Re: [Ql-Users] SMSQ/E and unset variables

I agree. Its annoying. In the mean time you could try DP's XREF utility. It lists all variables alphabetically together with the line number on which it is defined and on which it is used. This quickly reveals spelling mistakes and provides other useful debugging information. Works a doddle

[Ql-Users] SMSQ/E and unset variables

Hi all, When QDOS evaluates an expression and encounters a variable with no value assigned, it STOPs with “error in expression” and reports the line number. The programmer may well have made some spelling mistake, and can immediately make a correction. QDOS is doing exactly what the