In a message dated 14/04/05 14:38:06 GMT Daylight Time,
[EMAIL PROTECTED] writes:
[EMAIL PROTECTED] wrote:
As far as I know BP_LET changes a parameter by copying the value on
the maths stack to the address at byte 4 of the parameter entry on
the Name Table. I had assumed that this 4-byte
In a message dated 15/04/05 02:08:28 GMT Daylight Time,
[EMAIL PROTECTED] writes:
George Gwilt writes:
An array descriptor merely presents a logical view of the data. If Turbo
at present just sees that a parameter is an array and ignores any
indices,
then parsing those indices would
[EMAIL PROTECTED] wrote:
As far as I know BP_LET changes a parameter by copying the value on
the maths stack to the address at byte 4 of the parameter entry on
the Name Table. I had assumed that this 4-byte pointer would be set.
Instead MWDEF seems to be copying both the pointer into the name
In a message dated 12/04/05 12:01:19 GMT Daylight Time,
[EMAIL PROTECTED] writes:
[EMAIL PROTECTED] wrote:
The only snag I can see is if the code for MWDEF, which has to tell
whether the channel is sent by reference or value, gets it wrong for
Turbo. This could happen if, for example,
In a message dated 12/04/05 20:37:00 GMT Daylight Time,
[EMAIL PROTECTED] writes:
There are often good reasons for using array slices. Although work-arounds
are usually possible, they may require shifting data into other arrays which
is both time and space consuming.
An array descriptor
[EMAIL PROTECTED] wrote:
100 adr = MWDEF(#ch%)
110 REPeat loop
120 ch% = 0
130 action = MCALL(#adr)
140 if ch% 0: PRINT 'Error during MCALL:'! ch%: EXIT loop ...
How does line 120 indicate that ch% is the variable that MCALL is to
return the error code?
It doesn't, the MWDEF
[EMAIL PROTECTED] wrote:
The only snag I can see is if the code for MWDEF, which has to tell
whether the channel is sent by reference or value, gets it wrong for
Turbo. This could happen if, for example, MWDEF assumes (wrongly)
that the parameter is passed by value if the pointer to the Name
George Gwilt writes:
Turbo cannot set sliced arrays as parameters to S*BASIC procedures or
functions. This is because of the way the array descriptors are defined.
However it
is theoretically possible to set a sliced array as parameter to a machine
code
extension since Turbo defines an
Marcel Kilgus writes:
But I can change everything
Oh yes? ;)) One very simple improvement that could be made to MAWDRAW
would be to allow it to take an address instead of an array. The address
would point to a data area with the following structure - which you will
recognise as the last
P Witte wrote:
But I can change everything
Oh yes? ;))
Can, not will ;-)
One very simple improvement that could be made to MAWDRAW
would be to allow it to take an address instead of an array. The address
would point to a data area with the following structure - which you will
recognise
Marcel Kilgus writes:
P Witte wrote:
But I can change everything
Oh yes? ;))
Can, not will ;-)
I knew I must be dreaming.. ;)
One very simple improvement that could be made to MAWDRAW
would be to allow it to take an address instead of an array. The address
would point to a data
In a message dated 09/04/05 15:28:16 GMT Daylight Time,
[EMAIL PROTECTED] writes:
It sounds very promising! It must also be a major achievement as, IIUC,
Turbo gains some of its speed advantage by not mimicking certain SuperBasic
interpreter structures. Are these structures now being
In a message dated 09/04/05 15:28:16 GMT Daylight Time,
[EMAIL PROTECTED] writes:
All EasyPtr keywords can return an error code in the channel parameter,
provided it is supplied as an integer, ie #ch%.
That seems OK.
However, it gets more complicated: You can set EasyPtr up so
In a message dated 09/04/05 07:13:20 GMT Daylight Time,
[EMAIL PROTECTED] writes:
The latest beta test version of Turbo, v4d21, should soon be on the SQLUG
site. This one has compiled QPTR's demo_bas (after some modifications).
I'm curious, what kind of modifications? Dimensioning of
The latest beta test version of Turbo, v4d21, should soon be on
the SQLUG
site. This one has compiled QPTR's demo_bas (after some
modifications).
I'm curious, what kind of modifications? Dimensioning of strings?
I've read the readme of v4c21 and it sounds pretty promising. What
grade of
Dear George
Another of interest
John
- Original Message -
From: P Witte [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, April 09, 2005 3:27 PM
Subject: Re: [ql-users] Q-Starter
Marcel Kilgus writes:
[EMAIL PROTECTED] wrote:
The latest beta test version of Turbo, v4d21
[EMAIL PROTECTED] wrote:
The latest beta test version of Turbo, v4d21, should soon be on the SQLUG
site. This one has compiled QPTR's demo_bas (after some modifications).
I'm curious, what kind of modifications? Dimensioning of strings?
I've read the readme of v4c21 and it sounds pretty
Marcel Kilgus writes:
[EMAIL PROTECTED] wrote:
The latest beta test version of Turbo, v4d21, should soon be on the
SQLUG
site. This one has compiled QPTR's demo_bas (after some
modifications).
I'm curious, what kind of modifications? Dimensioning of strings?
I've read the readme of v4c21
Message-
From: Wolfgang Uhlig [mailto:[EMAIL PROTECTED]
Sent: 06 April 2005 17:46
To: [EMAIL PROTECTED]
Subject: Re: [ql-users] Q-Starter
Why did the chicken cross the road ?
What came first, the chicken or the egg ?
What do women want ?
Or:
Why is abbreviation such a long word
In a message dated 06/04/05 00:46:40 GMT Daylight Time,
[EMAIL PROTECTED] writes:
You bet! Besides, with all the work George put into Turbo it might
start being a real alternative. I've never been a fan of Turbo but
I think he's really moving something.
The latest beta test version of
[EMAIL PROTECTED] wrote:
Hmmm, this is a bit more difficult than I thought.
The compiler directive is correct, or at least as per what is in
ptrmen_cde ($$asmb=filename,4,82)
Seems strange that
the program would get past MDRAW and MITEM keywords and fail at
MSTAT%, I guess my
Shall we annoy Marcel and tell him he's working on QLiberator next ;-))
I think you would be taking your life in your hands
You bet! Besides, with all the work George put into Turbo it might
start being a real alternative. I've never been a fan of Turbo but
I think he's really moving
The compiler directive is correct, or at least as per what is in
ptrmen_cde ($$asmb=filename,4,82)
If the filename above should happen to be ptrmen_cde the correct parameters
are
$$asmb=filename,0,82
Per
I used ?,4,82 because that's what it says embedded in ptrmen_cde - I've always
The compiler directive is correct, or at least as per what is in
ptrmen_cde ($$asmb=filename,4,82)
If the filename above should happen to be ptrmen_cde the correct parameters
are
$$asmb=filename,0,82
Per
I used ?,4,82 because that's what it says embedded in ptrmen_cde -
MSTAT% is not in the redistributable code, it lives solely in the ptrmenR
code, ie, the resident stuff which you are not allowed to link into your
programs.
I'm pretty sure (ok, about 95%) that this will be your problem as I had it a
long time ago myself when DJC was still selling my
The compiler directive is correct, or at least as per what is in
ptrmen_cde ($$asmb=filename,4,82)
I just had a look and saw that ptrmen is broken, I've had 2 lines in
the wrong order.
Marcel
Thanks (again) Marcel, this should resolve the problem.
Serves me right for jumping the gun
Am Wed, 06 Apr 2005 08:01:59 +0100 hat [EMAIL PROTECTED]
geschrieben:
How about this :
MSTAT% is not in the redistributable code, it lives solely in the
ptrmenR code, ie, the resident stuff which you are not allowed to link
into your programs.
No, it doens't not. It's in the ptrmen_cde,
Marcel Kilgus writes:
P Witte wrote:
The compiler directive is correct, or at least as per what is in
ptrmen_cde ($$asmb=filename,4,82)
If the filename above should happen to be ptrmen_cde the correct
parameters
are
$$asmb=filename,0,82
No, 4,82 is the correct one. Address 4 is the
Norman Dunbar writes:
MSTAT% is not in the redistributable code, it lives solely in the
ptrmenR code, ie, the resident stuff which you are not allowed
to link into your programs.
I never noticed. But it definitely is in the runtime version of the toolkit
now, and has been since V3.50 at
[EMAIL PROTECTED] wrote:
No, it doens't not. It's in the ptrmen_cde, too.
Morning Wolfgang.
I did say that I was 95% sure - and it has been a long time since I had the
problem. The question now has to be, if it isn't MSTAT% then what EasyPtr
command was it I fell over on ?
We may never
Am Wed, 06 Apr 2005 12:21:48 +0100 hat [EMAIL PROTECTED]
geschrieben:
Hi Norman,
We may never know !
No problem, there are more things we may never know ;)
Wolfgang
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
[EMAIL PROTECTED] wrote:
Am Wed, 06 Apr 2005 12:21:48 +0100 hat [EMAIL PROTECTED]
geschrieben:
Hi Norman,
We may never know !
No problem, there are more things we may never know ;)
Indeed - such as :
Why did the chicken cross the road ?
What came first, the chicken or the egg ?
Indeed - such as :
Why did the chicken cross the road ?
What came first, the chicken or the egg ?
What do women want ?
Cheers,
Norman.
PS. The answer to the second one is 'the egg'. Birds (and therefore chickens)
are decendants of the dinosaurs and they laid egs - so, the egg came
P Witte wrote:
Im aware of the embedded message, but at some point I changed to
using 0,82 (ie dont call the initialisation routine at all)
No, this is not what's it doing:
QLiberator wants 2 parameters, one for the offset of an initialisation
routine that should NOT contain a call to sb.inipr
Why did the chicken cross the road ?
What came first, the chicken or the egg ?
What do women want ?
Or:
Why is abbreviation such a long word?
Is there another word for synonym?
etc ;)
Cheers, Wolfgang
___
QL-Users Mailing List
P Witte wrote:
Im aware of the embedded message, but at some point I changed to using 0,82
(ie dont call the initialisation routine at all) and it has apparently
worked. What deos the initialisation code do?
Oh dear, you're right. I didn't know 0 means do not call at all
and wouldn't have
- Original Message -
From: Marcel Kilgus [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, April 06, 2005 5:58 PM
Subject: Re: [ql-users] Q-Starter
Wolfgang Uhlig wrote:
Why is abbreviation such a long word?
Is there another word for synonym?
And in that vain: isn't dyslexic
PROTECTED]
Subject: RE: [ql-users] Q-Starter
Hi,
tried it got the Qlib error message :
Line 600 MSTAT% Invalid name
- an easy ptr extension?
Can you distribute the easy ptr runtimes with it?
Duncan Neithercut
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
tried it got the Qlib error message :
Line 600 MSTAT% Invalid name
- an easy ptr extension?
Can you distribute the easy ptr runtimes with it?
The runtimes are not distributable because they are part of the
commercial package but they can be compiled within the program itself.
...which is
In message
[EMAIL PROTECTED],
Dilwyn Jones [EMAIL PROTECTED] writes
Any news on the availability of the official Easyptr 4, Roy? Marcel did
mention some time ago he hoped it might be at the AGM, the money for
the upgrade is burning a hole in my pocket!
We are hoping for release at the AGM
- Original Message -
From: Dilwyn Jones
To: [EMAIL PROTECTED]
Sent: Tuesday, April 05, 2005 11:09 AM
Subject: Re: Re: [ql-users] Q-Starter
Any news on the availability of the official Easyptr 4, Roy? Marcel did
mention some time ago he hoped it might be at the AGM, the money
- Original Message -
From: Phoebus R. Dokos ( . )
To: [EMAIL PROTECTED]
Sent: Monday, April 04, 2005 9:14 PM
Subject: Re: [ql-users] Q-Starter
On Mon, 04 Apr 2005 15:06:37 -0400, Malcolm Cadman
wrote:
By the way QWord has its own Icon with QDT and launches successfully,
and drops back
for the new Easyptr
;-)
Dilwyn Jones
From: gwicks [EMAIL PROTECTED]
Date: 2005/04/05 Tue PM 07:01:36 GMT
To: [EMAIL PROTECTED]
Subject: Re: Re: [ql-users] Q-Starter
- Original Message -
From: Dilwyn Jones
To: [EMAIL PROTECTED]
Sent: Tuesday, April 05, 2005 11:09 AM
Subject: Re
In message [EMAIL PROTECTED],
=?windows-1253?B?UGhvZWJ1cyBSLiBEb2tvcyAo1u/f4u/yINEuIM30/Orv8ik=?=
[EMAIL PROTECTED] writes
On Mon, 04 Apr 2005 15:06:37 -0400, Malcolm Cadman
[EMAIL PROTECTED] wrote:
By the way QWord has its own Icon with QDT and launches successfully,
and drops back into
In message
[EMAIL PROTECTED],
Dilwyn Jones [EMAIL PROTECTED] writes
Hopefully, experience gained from writing this program will help and
encourage me to write more programs to take advantage of the new
facilities Marcel has worked so hard to bring us!
emailed Dilwyn privately to perhaps save embarrassment ...
From: Duncan Neithercut [EMAIL PROTECTED]
Date: 2005/04/04 Mon PM 08:22:08 GMT
To: [EMAIL PROTECTED]
Subject: RE: [ql-users] Q-Starter
Hi,
tried it got the Qlib error message :
Line 600 MSTAT% Invalid name
- an easy ptr extension?
Can you
Hi,
tried it got the Qlib error message :
Line 600 MSTAT% Invalid name
- an easy ptr extension?
Can you distribute the easy ptr runtimes with it?
Duncan Neithercut
Hmmm, this is a bit more difficult than I thought.
The compiler directive is correct, or at least as per what is in
ptrmen_cde
Dilwyn Jones wrote:
The compiler directive is correct, or at least as per what is in
ptrmen_cde ($$asmb=filename,4,82)
I just had a look and saw that ptrmen is broken, I've had 2 lines in
the wrong order.
Marcel
___
QL-Users Mailing List
Roy wood wrote:
Shall we annoy Marcel and tell him he's working on QLiberator next ;-))
I think you would be taking your life in your hands
You bet! Besides, with all the work George put into Turbo it might
start being a real alternative. I've never been a fan of Turbo but
I think he's really
Dilwyn Jones writes:
The compiler directive is correct, or at least as per what is in
ptrmen_cde ($$asmb=filename,4,82)
If the filename above should happen to be ptrmen_cde the correct parameters
are
$$asmb=filename,0,82
Per
___
QL-Users Mailing
P Witte wrote:
The compiler directive is correct, or at least as per what is in
ptrmen_cde ($$asmb=filename,4,82)
If the filename above should happen to be ptrmen_cde the correct parameters
are
$$asmb=filename,0,82
No, 4,82 is the correct one. Address 4 is the entry point without
sb_inipr, 0
In message [EMAIL PROTECTED], Dilwyn Jones
[EMAIL PROTECTED] writes
Q-STARTER
Q-Starter is a simple experimental program to see if I can
successfully create a program which will run on anything from a QDOS
system with pointer environment to the latest Window Manager 2 and use
the System Palette.
Hopefully, experience gained from writing this program will help and
encourage me to write more programs to take advantage of the new
facilities Marcel has worked so hard to bring us!
http://homepages.tesco.net/dilwyn.jones/software/freeware/freeware.html
Thanks, Dilwyn. I will download
On Mon, 04 Apr 2005 15:06:37 -0400, Malcolm Cadman [EMAIL PROTECTED]
wrote:
By the way QWord has its own Icon with QDT and launches successfully,
and drops back into QDT, even though there is a colour mode change on my
system.
Yes, Jim had the foresight to ask us to create one ahead of
To: QL Users List
Cc: QL News List
Subject: [ql-users] Q-Starter
Q-STARTER
Q-Starter is a simple experimental program to see if I can
successfully create a program which will run on anything from a QDOS
system with pointer environment to the latest Window Manager 2 and use
the System Palette
In message [EMAIL PROTECTED], Duncan
Neithercut [EMAIL PROTECTED] writes
Hi,
tried it got the Qlib error message :
Line 600 MSTAT% Invalid name
- an easy ptr extension?
Can you distribute the easy ptr runtimes with it?
The runtimes are not distributable because they are part of the
commercial
Q-STARTER
Q-Starter is a simple experimental program to see if I can
successfully create a program which will run on anything from a QDOS
system with pointer environment to the latest Window Manager 2 and use
the System Palette. It is also my first attempt at writing a program
to use scalable
57 matches
Mail list logo
