On 30 Apr 2012, at 14:05, Marcel Kilgus wrote:
Bob Spelten wrote:
Nothing to do with BPUT here. The problem is that you're using an
array expression x(0,1) with more than one dimension in the FOR loop.
SBASIC got a bug there.
Thanks for the insight.
I was puzzled because it had worked
Op Mon, 30 Apr 2012 00:12:28 +0200 schreef Marcel Kilgus
ql-us...@mail.kilgus.net:
Bob Spelten wrote:
Can anyone explain this?
I found another UPUT/BPUT related strange bug.
I have the following lines in my program:
FOR i%= 0 TO x(0,1) -1 : BPUT #c3%,aa$
Nothing to do with BPUT here. The
Op Mon, 23 Apr 2012 10:20:14 +0200 schreef Bob Spelten b...@upcmail.nl:
Can anyone explain this?
I found another UPUT/BPUT related strange bug.
I have the following lines in my program:
FOR i%= 0 TO x(0,1) -1 : BPUT #c3%,aa$
When run this stops with:
at line 1252:3 undefined loop control
Can anyone explain this?
I have the following line in a program:
: aa$= PEEK$(address,length): UPUT #c3%,aa$
This reads a line from screen memory and writes this to a _pic file on
win1_.
The ten byte header has already been written to the file channel with
BPUT's.
Qlib reported an error
Bob,
is aa$, by any chance, a LOCal variable?
Qlib sometimes reports LOCal variables as parameters to external PROCs as
invalid.
Regards,
Tobias
-Original-Nachricht-
Von: Bob Spelten b...@upcmail.nl
An: ql-us...@q-v-d.com ql-us...@q-v-d.com
Betreff: [Ql-Users] UPUT Qubide
Datum: Mon
