Tobias,
the manual ist stated as "2nd Edition". I have got it with release 3.22a.
OK, I have read further: There are additional sheets (a page 15.8, put in
later by myself when I got rel.3.3 from them) for rel.3.3: I quote:
"The concept of free running procedures was introduced on page 14.9 of the
user manual. In releases prior to 3.3, such procedures could only be started
from the interpreter. 3.3 removes this restriction and allows compiled
programs to spawn independent jobs by a single procedure call."
It should work...
Cheers...Ralf
----- Original Message -----
From: <tobias.froesc...@t-online.de>
To: <ql-us...@q-v-d.com>
Sent: Thursday, January 08, 2009 11:50 AM
Subject: Re: [Ql-Users] QLIB Free-Running Procedures
Ralf,
my manual doesn't mention the restriction to the interpreter. What
version do you have?
The problem is, it seems to work halfway - The procedure actually does
run in a separate job - But it seems to fail to signal completion to the
parent job and the parent job just hangs.
I'll have a try on native QDOS - Maybe it works there?
It would be nice if it worked, however. I used to use the "EX" method
mentioned by George, but this gives you problems locating the daughter
job's code file in the file system (I know I could work around this with
the HOME_DIR). But I would just like to have everything in one single
self-contained binary.
Regards
Tobias
-----Original Message-----
Date: Thu, 08 Jan 2009 11:35:18 +0100
Subject: Re: [Ql-Users] QLIB Free-Running Procedures
From: Ralf Reköndt <ralf.rekoe...@t-online.de>
To: <ql-us...@q-v-d.com>
Tobias,
there seem to be one important sentence in this section about "Free
running
procedures" about starting the job with an "!":
"This feature is restricted to the the interpreter only in this
release".
Perhaps it does not work in a compiled program (maybe in a separate
daughter
SBASIC).
Cheers...Ralf
----- Original Message -----
From: Tobias Fröschle
Sent: Thursday, January 08, 2009 9:56 AM
Subject: Re: [Ql-Users] QLIB Free-Running Procedures
BTW: The "worker" procedure _is_actually executed in a job of its own.
But it does seem to never return to main.
-----Original Message-----
What I saw is one single execution of the procedure worker. This then
runs to an end, main just hangs there doing nothing (suspended, but
not
ended).
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
