Op 23/11/2022 om 16:40 schreef pjwitte via Ql-Users:
On 23/11/2022 14:51, François Van Emelen via Ql-Users wrote:
Op 22/11/2022 om 13:26 schreef pjwitte via Ql-Users:
Does anyone know whats going on here?
<>
Could this solve your problem?
100 ch = FOPEN("con"): CLS#ch
110 test ch, 25
120
On 23/11/2022 14:51, François Van Emelen via Ql-Users wrote:
Op 22/11/2022 om 13:26 schreef pjwitte via Ql-Users:
Does anyone know whats going on here?
<>
Could this solve your problem?
100 ch = FOPEN("con"): CLS#ch
110 test ch, 25
120 print#ch,"hit a key to stop" :PAUSE#ch,-1
130 CLOSE#ch
Hi,
Per wrote:
> Perhaps you didnt EX it? If you RUN it it may work, although a
> differently constructed (more complex) version would also fail.
I didn't ex it, just ran it - the problem was already seen under an
SBasic daughter job.
Derek wrote:
It looks like the variable for the FOPEN
Hi
I changed the ch in the FOPEN variable to chan and it worked with EX, SBAS.
It looks like the variable for the FOPEN parameter is getting mixed up with the
parameter on the Procedure parameter.
I also tried the original program on Minerva with MultiBasic executing the
program with: EX
Op 22/11/2022 om 13:26 schreef pjwitte via Ql-Users:
Does anyone know whats going on here?
SBASIC only: EXecute the following program:
100 ch = FOPEN("con"): CLS#ch
110 test ch, 1
120 PAUSE#ch
130 CLOSE#ch
140 :
150 DEFine PROCedure test(ch, a)
160 PRINT#ch; a
180 END DEFine test
Result in
Perhaps you didnt EX it? If you RUN it it may work, although a
differently constructed (more complex) version would also fail.
Anyway, its not about the platform, its about SMSQ/E. Ive tried it on
SMSQ/E V3.25, 3.38 and 3b39 - all present with the same problem.
Per
On 22/11/2022 16:38,
RUNing appears to work; its when EXing this program that the problem
shows up.
I believe its possible to get an error on RUNing too, I just havent
been able to recreate the conditions.
Typical errors are:
At line nnn:
At line : undefined loop control
variable
etc, all nonsense
Clearly,
Hi,
Does anyone know whats going on here?
Nope...
Even stranger : once you run this and it failed, change the variable
name ("ch") to something else (like "cht") everywhere . Run it - and it
works. Save the prog with that new variable name, start a new basic
session, load the prog, run
Does anyone know whats going on here?
SBASIC only: EXecute the following program:
100 ch = FOPEN("con"): CLS#ch
110 test ch, 1
120 PAUSE#ch
130 CLOSE#ch
140 :
150 DEFine PROCedure test(ch, a)
160 PRINT#ch; a
180 END DEFine test
Result in this case:
At line 150:4 DEFines may not be within
