Re: FW: questions about threads

Please clarify if you are using "threads" or "tasks" in the SwiftForth
model.
A thread is very different from a task, and if you are trying to use the
task
management words such as ACTIVATE on a true thread, there are going
to be problems.
rick

On 8/22/06, Dr. Roger Dube <rogerdube_at_dathq.com> wrote:
>
>
> We are using threads for specific subtasks in some code, and we have some
> questions.
>
>
>
> 1. What is the significance of the 4096 B TCB space allocated to a
> thread? How would we know when we need to make it bigger?
> 2. ACTIVATE returns something to the stack, but the book does not say
> it should – what is the significance of this value? How do we know if the
> thread has been started successfully?
> 3. How do we pass a value to a thread without using a global
> variable?
> 4. When we KILL a thread, we get something back on the stack, even
> though the documentation does not say that… can someone tell us the
> significance of that information?
>
>

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
For list command help, send subject "help" to sftalk-request_at_forth.com
Message archives are located at http://www.forth.com/archive/sftalk
----------------------------------------------------------------------
This list is a forum for SwiftForth users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Tue Aug 22 2006 - 08:22:02 PDT