Hi,
If I understand the circumstances correctly, I would handle the chicken
and egg problem differently.
The circumstances are that you're trying to develop a BOOT program,
which loads a certain set of extensions. You want to avoid loading the
extensions again if the BOOT program is run
...@q-v-d.com
Cc: Derek
Subject: Re: [Ql-Users] TURBO and testing it exists
Hi George,
I proposed in th QL Forum adding a S or Q in the TK_VER$.
But your proposed new Function sounds a good idea.
RegardsDerek
Original message From: gdgqler--- via Ql-Users
<ql-users@lists.q-v-d.
: gdgq...@gmail.com Subject: Re: [Ql-Users] TURBO and
testing it exists
> On 19 Aug 2017, at 09:21, gdgqler--- via Ql-Users <ql-users@lists.q-v-d.com>
> wrote:
>
> I would think it possible to have TK_VER$ print “TK”, “SMS” or “REM” after
> the version number. Is this what p
Hi,
The link works for me, even on an android tablet...
Regards,
Derek
Original message
From: Per Witte via Ql-Users <ql-users@lists.q-v-d.com>
Date: 19/08/2017 13:13 (GMT+00:00)
To: ql-us...@q-v-d.com
Cc: Per Witte <pjwi...@online.no>
Subject: Re: [Ql-
Hi Michael, I dont know why it doesnt work for you. I just clicked on the
link now and it works for me. Try copying the link and pasting it in your
browser. The article is about searching for specific keywords in
SuperBASIC, SBASIC and compiled BASIC without the use of an external
toolkit.
Per
PS
> On 19 Aug 2017, at 09:21, gdgqler--- via Ql-Users
> wrote:
>
> I would think it possible to have TK_VER$ print “TK”, “SMS” or “REM” after
> the version number. Is this what people would like?
It might be better to have a new keyword, TK_TYPE$, which would return
Your approach is commendable as an option for those who dont load a Turbo
toolkit by default, but for the rest of us it doesnt do much good.
Presumably, the REM version is based on the generic version which is
somewhat less optimal under SMSQ/E? And Turbo-compiled tasks will use the
incorporated
On Thu, 17 Aug 2017 21:08:31, Per Witte wrote:
> Thats a nice solution. Not sufficient for all manner of keywords, though.
A
> more general solution for checking for relevant toolkits in boot programs,
> without having to load a toolkit to do so can be found
string as
though it was a number, so adding the version letter as a 5th digit is
probably better.
Dilwyn
-Original Message-
From: gdgqler--- via Ql-Users
Sent: Saturday, August 19, 2017 9:21 AM
To: ql-us...@q-v-d.com
Cc: gdgq...@gmail.com
Subject: Re: [Ql-Users] TURBO and testing
> On 17 Aug 2017, at 10:25, Tobias Fröschle via Ql-Users
> wrote:
>
>> There is a keyword: TK_VER$, but only returns the version of Turbo Toolkit,
>> which is the same for the SMS and QDOS versions.
I would think it possible to have TK_VER$ print “TK”, “SMS” or “REM”
> On 18 Aug 2017, at 17:38, Per Witte via Ql-Users
> wrote:
>
> George, the question is relevant if you write programs intended for other
> people: You cant be sure THEY will load Turbo. However, IMHO, any serious
> Tinkerer should load Turbo as a matter of course.
I
Simply load one of the thousand "is there that toolkit name" extensions
like "ISIT" (Disassembler from DP) or similar and you are happy. Even
Dilwyn has one on his site.
There is also a very old little toolkit from Steve Jones (Sidewinder),
which can put every resident Procedure into an
George, the question is relevant if you write programs intended for other
people: You cant be sure THEY will load Turbo. However, IMHO, any serious
Tinkerer should load Turbo as a matter of course.
Per
On 18 August 2017 at 16:54, gdgqler--- via Ql-Users <
ql-users@lists.q-v-d.com> wrote:
>
> >
Ah, very clever ;-)))
gdgqler--- via Ql-Users:
On 17 Aug 2017, at 13:54, Lee Privett via Ql-Users wr
I feel there must be a way to test for TURBO toolkit, any ideas?
In my BOOT I load the TURBO toolkit. So why should I test for it?
If I don’t load it in my BOOT it
> On 17 Aug 2017, at 13:54, Lee Privett via Ql-Users
> wr
> I feel there must be a way to test for TURBO toolkit, any ideas?
In my BOOT I load the TURBO toolkit. So why should I test for it?
If I don’t load it in my BOOT it just is not loaded.
George
t;
Sent: Thu, 17 Aug 2017 18:14
Subject: Re: [Ql-Users] TURBO and testing it exists
Perhaps I should clarify this a little further.Using Q-emuLator, my boot first
loads SMSQ_QEM and restarts with the sameboot, I will always do this or use
QPC2, I am not really looking for a BBQLsolution as
Thats a nice solution. Not sufficient for all manner of keywords, though. A
more general solution for checking for relevant toolkits in boot programs,
without having to load a toolkit to do so can be found in this article:
http://www.hunggartorino.it/ql/findkey/ (also available in Italian!)
Per
2017 10:25 AM
To: ql-us...@q-v-d.com
Cc: Tobias Fröschle
Subject: Re: [Ql-Users] TURBO and testing it exists
Lee,
there are a number of toolkits that allow you to check for specific
other toolkit commands loaded or not - But this is a bit useless as it
leaves you with a chicken-and-egg problem:
Thanks for all the suggestions guys,
220 IF TK_VER$<>"" THEN
230 PRINT "Done":STOP
240 ELSE
250 LRESPR win8_turbo_sms_code
260 END IF
this works exactly how I wanted it to, so to Tobias.
Many thanks to you all
Lee
Lee
On Thu, Aug 17, 2017 at 11:47 AM, Tobias Fröschle via
Lee,
in case your question is really only Turbo Toolkit specific, you can very well
do away with a much simpler solution than WHEN ERRor clauses:
1000 IF TK_VER$ <> ""
1010 REM do whatever you want to do when Turbo Toolkit is loaded
1020 ELSE
1030 REM Do whatever you want to do if it is not
from another toolkit of course)
Not the full answer you were hoping for but one which can cope with most
situations apart from unexpanded BBQL.
Dilwyn
-Original Message-
From: Tobias Fröschlevia Ql-Users
Sent: Thursday, August 17, 2017 10:25 AM
To: ql-us...@q-v-d.com
Cc: Tobias Fröschle
Su
Perhaps I should clarify this a little further.
Using Q-emuLator, my boot first loads SMSQ_QEM and restarts with the same
boot, I will always do this or use QPC2, I am not really looking for a BBQL
solution as it is development for other things.
Where this
[code]IF VER$<>"HBA" THEN
LRESPR
Hi Tobias,
The WHEN solution is great, but on some version of QODS, the WHEN ERRor
did not work.
There are some people still using AH,JM, roms which may have problems
with WHEN ERRor
--
Regards,
Derek
On 17/08/17 10:39, Tobias Fröschle via Ql-Users wrote:
After I sent this, I realised a
Hi,
Would it be possible to add in a code letter in TK_VER$ for each version
of Turbo Toolkit, i.e.
TK_VER$ for SMS, 3.40s
--
Regards,
Derek
On 17/08/17 10:25, Tobias Fröschle via Ql-Users wrote:
Lee,
there are a number of toolkits that allow you to check for specific other
toolkit
After I sent this, I realised a bit of explanation might be in order, as WHEN
ERRor is not so well-known:
When the interpreter passes a WHEN ERRor/END WHEN pair during normal program
execution, it doesn't do anything with the commands inside the clause but
remembering "I should do this in case
Lee,
there are a number of toolkits that allow you to check for specific other
toolkit commands loaded or not - But this is a bit useless as it leaves you
with a chicken-and-egg problem: How to check whether the checking toolkit is
loaded?
Your best bet on SMSQ/E would be a WHEN ERRor clause
26 matches
Mail list logo