Re: [Amforth-devel] string output problem while using lib/multitask.frt

[Matthias T. <mt...@we...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Erich,

> and it does exactly, what it should. However, calling the
> contents of message "manually", fails to show on the terminal:
> 
>    > ." c2_null_from_prompt"
>     ok
> 
> Note that the string did not show up. Is this a bug or a
> feature? This looks like a feature to me.

Quoting ANS94
- -----------------
6.1.0190 ."
dot-quote CORE

        Interpretation: Interpretation semantics for this word are
undefined.

        Compilation: ( "ccc<quote>" -- )

Parse ccc delimited by " (double-quote). Append the run-time semantics
given below to the current definition.

        Run-time: ( -- )

- ------------------

I agree that most systems support an interpretation semantic similar to
the run-time of the compiled word, but I decied against. Mostly to have
a system that runs on 8 KB flash...

> Now I start the tasker. I expect the count in c0 to increase,
> and occasionally the message to show up.
> 
>    > c0 @ u.
>     50964 ok
>    > multi
>     ok
>    > c0 @ u.
>     53896 ok
> 
> The counter does increase indeed, however, the message does show
> up only partially.
> 
>    > >
>    > c2_
> -------^ stops here! no " ok", no newline, no "> "

Does the system still accept any commands (simply hit <ret>)?

> It looks like the string is not handled correctly, since calling
> message manually does work:
> 
>    > message
> 
>    c2_null_msg ok
> 
> Is this a bug or a feature? Looks like a bug to me anyway.

Me too. But not in the multitasker. The serial O code (output
part) was inteded to use a queue, but it turns out, that the
code only looks like using a queue, but in fact does not use it
at all. I'll fix it, but only ASAP ....

Matthias

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHhTYi9bEHdGEMFjMRAtoeAJ9ZtSh3E5mfed1IYoJ7og4Pzp4t9QCfbYaI
Kp+VDcJA+++4nrzpE9/Qehw=
=DagZ
-----END PGP SIGNATURE-----