Hi,
I personally would have no problem with adding a UQLX type into the
SMSQE "keys_sys" file, at sys_mtyp (offset A7, as Per pointed out).
Wolfgang
> The bits in the SMSQmulator readme and QPC Keywords manuals that
> describe the JVA_xxx/QPC_xxx keywords.
>
> EMU_EXIT, EMU_VER$,
I'm a bit late to this conversation so may be missing the point - there is
some documentation regarding the use of the Machine system variables and
functions on my website, at http://www.dilwyn.me.uk/docs/articles/index.html
- scroll down to the Machine Type... articles. They're rather old so may
On 06/07/2021 16:51, Graeme Gregory via Ql-Users wrote:
On Tue, 6 Jul 2021, at 3:44 PM, pjwitte via Ql-Users wrote:
<>
If it were only that easy.. :o(
I havent gone through all of it, but just a couple of things:
MACHINE would be better for sorting out wots wot, except not all
systems
On Tue, 6 Jul 2021, at 3:44 PM, pjwitte via Ql-Users wrote:
> On 06/07/2021 16:18, desin via Ql-Users wrote:
> > Am 06.07.21 um 15:07 schrieb Graeme Gregory via Ql-Users:
> >>
> >>
> >> On Tue, 6 Jul 2021, at 1:59 PM, desin via Ql-Users wrote:
> >>>
> I agree with Francois, using LOOKUP% as
On 06/07/2021 16:18, desin via Ql-Users wrote:
Am 06.07.21 um 15:07 schrieb Graeme Gregory via Ql-Users:
On Tue, 6 Jul 2021, at 1:59 PM, desin via Ql-Users wrote:
I agree with Francois, using LOOKUP% as alternative for EXISTS.
I use it a lot. It returns the place in the name table which
Hi,
I would do it the other way around. First check for "HBA" in vers$, if
it is that then you're on SMSQE and you can use the return from the
MACHINE function to find out what machine you're on.
Wolfgang
> On the other hand; would it be safe to presume; for all Systems;
> if SCR_XLIM is
Am 06.07.21 um 15:07 schrieb Graeme Gregory via Ql-Users:
On Tue, 6 Jul 2021, at 1:59 PM, desin via Ql-Users wrote:
I agree with Francois, using LOOKUP% as alternative for EXISTS.
I use it a lot. It returns the place in the name table which can also be
used to test for conflicting keywords
On Tue, 6 Jul 2021, at 1:59 PM, desin via Ql-Users wrote:
>
> > I agree with Francois, using LOOKUP% as alternative for EXISTS.
> > I use it a lot. It returns the place in the name table which can also be
> > used to test for conflicting keywords if found out of place.
> >
> > Bob
> >
> on
I agree with Francois, using LOOKUP% as alternative for EXISTS.
I use it a lot. It returns the place in the name table which can also be
used to test for conflicting keywords if found out of place.
Bob
on QDOS
Lookup% can not distinguish between
SCR_XLIM and SCRXLIM
On 06/07/2021 14:13, Wolfgang Lenerz via Ql-Users wrote:
Hi Per,
an interesting pitfall, thanks for pointing that out.
It does seem that Qlib sets the value of the repeat loop control
variable to 0 at the start of the loop.
Do you know how this fares on plain QDOS, not SMSQE?
Regards
Hi Per,
an interesting pitfall, thanks for pointing that out.
It does seem that Qlib sets the value of the repeat loop control
variable to 0 at the start of the loop.
Do you know how this fares on plain QDOS, not SMSQE?
Regards
Wolfgang
> I dont know if this has been documented anywhere,
I have encountered this before, but, like Bob said, assumed it was just a
question of a new type of variable being set up. In other words, I assumed
I was doing something wrong and simply avoided whatever was happening.
Dilwyn
On Tue, 6 Jul 2021, 11:55 Bob Spelten via Ql-Users, <
pjwitte via Ql-Users wrote:
I dont know if this has been documented anywhere, but Im putting it out
here as it caused me some grief.
It appears that Q-Liberator zeroes the loop variable on entry to a loop.
The following demo, which is acceptable (although perhaps not very
elegant) S*BASIC,
I dont know if this has been documented anywhere, but Im putting it
out here as it caused me some grief.
It appears that Q-Liberator zeroes the loop variable on entry to a
loop. The following demo, which is acceptable (although perhaps not
very elegant) S*BASIC, will not work in the same way
14 matches
Mail list logo
