I am please to advise that after further negotiation with the Allesley
Hotel, Coventry, Sarah has managed to get the original quotation for Bed &
Breakfast Accommodation reduced by over 27%. The revised rates are:-
Single Room B & B £47.00 per night
Twin or Double Room B & B £53.00 per night.
tobias.froesc...@t-online.de wrote:
> Suspecting my problems could be caused by some other extensions my boot
> program loads, I tried a clean boot with only QLiberator runtimes -
> still no luck.
I had a quick jab at debugging the problem. As far as I can see this
is a race condition.
The main j
Wolfgang,
watch me baffled!
Suspecting my problems could be caused by some other extensions my boot
program loads, I tried a clean boot with only QLiberator runtimes -
still no luck.
What version of QLiberator are you using? Mine seems to be 3.34
(runtimes) and 3.33 (compiler).
Regards
Tobias
---
Hi,
I've tested your prog and here it seems to work - I get plenty of "worker" jobs
opening plenty of
windows
Wolfgang
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
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 o
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
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).
On 8 Jan 2009, at 08:56, tobias.froesc...@t-online.de wrote:
-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).
It looks good written for Turbo. Of course you nee
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).
___
