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,
Yes, it works perfectly!
Thanks for your advice which has become fundamental for me
Do you think I wrote on the mailing list because I didn't want to disturb
you. :-)
Regards
Gio
P.Š. I looked at those things that you added on your fantastic site
. WOW
Il giorno dom 22 mar 2020
I was just pointing out, to anyone interested, that there is a lot
more one can do with this ;o) Obviously a myprog_bas program has to
exist and be valid, and the exclamation mark was informative and not
meant to be part of the command.
But EXEP 'SBASIC' should do what I presume you were
that's not true, it works
Didn't I just understand the use of the exclamation mark?
Il giorno dom 22 mar 2020 alle ore 21:35 Giorgio Garabello <
g.garabe...@gmail.com> ha scritto:
>
>
> Il giorno dom 22 mar 2020 alle ore 18:22 pjwitte via Ql-Users <
> ql-users@lists.q-v-d.com> ha scritto:
>
>>
Il giorno dom 22 mar 2020 alle ore 18:22 pjwitte via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:
> Try EXEP 'SBASIC',
this work well!
> or even EXEP 'SBASIC'; 'lrun"myprog_bas"'!
>
this not
Giorgio
>
> Per
> On 22/03/2020 17:52, Giorgio Garabello via Ql-Users wrote:
> > I'm trying to
Try EXEP 'SBASIC', or even EXEP 'SBASIC'; 'lrun"myprog_bas"'!
Per
On 22/03/2020 17:52, Giorgio Garabello via Ql-Users wrote:
I'm trying to run the SBASIC command inside a compiled program (with
Qliberator) but nothing happens .
Ideas?
100 PRINT "STEP 1"
110 SBASIC
120 PRINT "STEP 2"
On 28/06/2018 09:03, Wolfgang Lenerz via Ql-Users wrote:
Hi,
I made a small Sbasic testcase (SMSQE, not QDOS).
I made a program with procedures all called "abcdefghijklmnopqrt"+ a 5
digit number at the end.
The program starts at line 100, is increased by one and very 12th line a
new 10 line
I think it depends on which types of variables you're coercing...
In this case, because integers are stored as floats and are a wicked lie,
ints and floats are already the same thing logically speaking. So the only
invalid coercion is string to float where the string contents are of the
wrong
Hi,
I made a small Sbasic testcase (SMSQE, not QDOS).
I made a program with procedures all called "abcdefghijklmnopqrt"+ a 5
digit number at the end.
The program starts at line 100, is increased by one and very 12th line a
new 10 line procedure is created. The first statement therein is
Hi,
I can't help but wonder whether the time taken to parse all your
parameters to check whether they are the right type won't be longer than
having several procedures.
Wolfgang
> I'll make sure to respond right away in future, before I've fully
> understood the subtleties and implications of
Im not familiar with C++ overloading, but S*BASIC allows some "parametric
polymorphism", viz:
dim x%(2): for i% = 0 to 2: x%(i%) = 9 - i%
Test 'abc', 2.99, x%
:
def proc Test(a, b%, c)
print a\ b% \ c, \
enddef Test
:
Result:
abc
2.99
9 8 7
The SBASIC compiler performs a number of additional
On 21 June 2018 at 15:21, Dave Park via Ql-Users
wrote:
> > SuperBASIC is quite unique in that it stores the *difference* in length
> of
> > a line compared to the previous line, along with its line number. This
> way,
> > because the current line length is also stored in a system variable, it
>
On Thu, Jun 21, 2018 at 3:13 AM, Jan Bredenbeek via Ql-Users <
ql-users@lists.q-v-d.com> wrote:
> SuperBASIC is quite unique in that it stores the *difference* in length of
> a line compared to the previous line, along with its line number. This way,
> because the current line length is also
On 21 June 2018 at 00:43, Dave Park via Ql-Users
wrote:
> My reason for asking was, I was wondering if an analysis of how frequently
> functions were called, and from where, could affect how quickly they would
> be stepped to. I have seen this behavior in SuperBASIC on JM/JS and
> achieved often
My reason for asking was, I was wondering if an analysis of how frequently
functions were called, and from where, could affect how quickly they would
be stepped to. I have seen this behavior in SuperBASIC on JM/JS and
achieved often useful gains in improvements by placing the most frequently
On 20 June 2018 at 22:35, Dave Park via Ql-Users
wrote:
> Hi all,
>
> Separately, does the sBASIC in SMSQ or Minerva still scan for
> procedures/functions from the beginning of the program, so earlier FN/PROCs
> have a speed advantage over later ones like in JM/JS?
SuperBASIC (JM/JS/Minerva)
>> To save you reinventing the wheel Jan, Norman Dunbar's DJToolkit has an
> extension called LEVEL2 which tests for a Level 2 filing system. The
> assembler source djtoolkit_asm is included with the toolkit - just search
> for 'level2' in that source.
>
> http://www.dilwyn.me.uk/tk/djtk.zip
>
- NOTE: On non-V2 drivers which don't support subdirectories, ls will
fail
because the FNAME$ function stops with 'bad parameter' on directory
channels. This can be avoided by adjusting line 1710 in the code (as
indicated in the REMarks). I'll probably have to design another machine
code call to
On 2017-02-12 16:43, Jan Bredenbeek wrote:
On 12 February 2017 at 15:29, RWAP Software
wrote:
Hi Jan,
That is great - it is a nice function which can be useful.
Could I ask you to consider moving (or Forking?) the repository to the
new
SInclair QL Github, as this
On 12 February 2017 at 15:29, RWAP Software wrote:
> Hi Jan,
>
> That is great - it is a nice function which can be useful.
>
> Could I ask you to consider moving (or Forking?) the repository to the new
> SInclair QL Github, as this is intended to keep all of the QL
Hi Jan,
That is great - it is a nice function which can be useful.
Could I ask you to consider moving (or Forking?) the repository to the
new SInclair QL Github, as this is intended to keep all of the QL stuff
together -
https://github.com/SinclairQL
Rich
On 2017-02-12 14:24, Jan
I've updated the code with various improvements and fixes:
- Listing now adjusts to window size and can be aborted by pressing 'Q' or
ESC, even when recursing directories;
- Redirection by DEV device is now handled correctly (so long as you don't
rename the DEV device itself ;))
- SMSQ is no
On 26 Mar 2009, at 08:59, Christopher Cave wrote:
Does anyone know what the SBasic thing expects on the stack when it is
used? Or can anyone please tell me where the appropriate documentation
can be found (I have the SMSQ source but no idea where in it to look)?
Looking at Jonathan Hudson's
On 11 Aug 2007, at 13:57, Dilwyn Jones wrote:
PAR_WAIT (presumably something to do with parallel port)
This is part of SMSQ/E but its definition is not in my QPC2 manual.
The code seems to set a pause for a period of time. Perhaps the
author knows what for?
George
George Gwilt wrote:
PAR_WAIT (presumably something to do with parallel port)
This is part of SMSQ/E but its definition is not in my QPC2 manual.
The code seems to set a pause for a period of time. Perhaps the
author knows what for?
That would be Tony.
According to the QDOS Classic
Looking at a list of SBASIC extensions created with an EXTRAS
command,
there are 3 extensions I noticed that I don't know what they do.
Not
in my (admittedly old) manual. Anyone know?
CHK_HEAP (Some form of heap check suggested by the name)
HOME_CSET (presumably
Dilwyn Jones writes:
Looking at a list of SBASIC extensions created with an EXTRAS
command,
there are 3 extensions I noticed that I don't know what they do. Not
in my (admittedly old) manual. Anyone know?
CHK_HEAP (Some form of heap check suggested by the name)
HOME_CSET
33 matches
Mail list logo