Hello Erich,
I revisited "Redirecting emit from within a task in AmForth",
as I still like the idea of having a self contained task that can
perform its own io, but without having to write my own version of
pictured numeric output.
The bug was in my understanding, rather than anything else.
It
Hello Erich,
Thank you for looking at my code.
I will stick with not redirecting EMIT within a task (though I do still like
the idea of it).
Thanks and best wishes,
Tristan
> On 7 Oct 2019, at 20:34, Erich Wälde wrote:
>
> Hello Tristan,
>
> I just spent some time on your problem.
>
>
Hello Tristan,
I just spent some time on your problem.
1. I can reproduce this problem with your code! Your code looks
innocent to my eyes, with the possible exeption of changing "
emit? " as well. But leaving that out does not change the
problem.
2. stack size
I replaced
> 1 +noop . -noop
Hello Erich,
Thank you for your email.
The example I posted was the simplest I could think of that would
illustrate the what I was trying to achieve - the redirection of EMIT
within a task. What I actually have is various sensors attached to an
AVR. Rather than poll each of them in a loop I
Hello Tristan,
I need to look into my stuff, but that won't happen before next
week. If I understand you correctly, you want to "shut down the
output of the task, no matter what." I think, I have done this
somewhere ... but I do not remember the details. You need to
place " ' drop " in the
