They are tested for compilation, not that they generate the desired
results (though this is a wishlist item in the docs backlog)
On Tue, Jan 5, 2021 at 9:59 AM Ralph Mellor wrote:
>
> Sounds to me like it's time to raise a doc issue.
>
> Also, does anyone know if doc examples are tested?
>
>
Sounds to me like it's time to raise a doc issue.
Also, does anyone know if doc examples are tested?
Not just when first published, but as part of blinning?
On Tue, Jan 5, 2021 at 1:30 PM Theo van den Heuvel
wrote:
>
> Hi gurus,
>
> The first example in the documentation on the start control
What is happening is that the `start` happens on another thread.
That thread is not the main thread.
The program exits when the main thread is done.
Since the main thread doesn't have anything else to do it exits before that
`sleep` is done.
The more correct way to handle it would be to wait for
thanks. That helps.
Elizabeth Mattijsen schreef op 2021-01-05 14:37:
If those are the only lines in your program, the program will have
exited before the sleep in the start has actually passed. If you
change the program to:
start { sleep 1; say "done"; exit }
say "working";
sleep;
If those are the only lines in your program, the program will have exited
before the sleep in the start has actually passed. If you change the program
to:
start { sleep 1; say "done"; exit }
say "working";
sleep;
you should also see the "done".
> On 5 Jan 2021, at 14:15, Theo van
Hi gurus,
The first example in the documentation on the start control flow does
not seem to work as promised.
Here is the code:
start { sleep 1; say "done" }
say "working";
# working, done
Both 2020.1 and the 2020.12 version under Ubuntu yield only "working".
Am I missing something?
--
