Re: TASK HALT with another task

At 08:03 AM 8/10/2003 -0700, you wrote:

...
> > > A task could execute the STOP instruction within itself to stop.

Yes, that is how a task deactivates itself. However, once STOPped
it cannot start up again on its own; it needs to be started by another
task.

>...
> > : READSWITCHES
> >
> > PIND C@ 254 =
> > IF TESTER HALT
> > ELSE PIND C@ 253 =
> > IF TESTER ACTIVATE
>
>You can't have an activate without anything following it. Where is your
>endless loop? I think you mean:
> > IF TESTER ACTIVATE SEQBITFLASH
>
> > THEN
> > THEN ;

Noel is right, ACTIVATE needs to be followed by the code the
task is supposed to execute. And remember, it's essential
that the ACTIVATEd task never reach the end of the definition.

This definition is where you should use your vectored
execution table. The definitions there can include
ACTIVATEs.

Cheers,
Elizabeth

==================================================
Elizabeth D. Rather (US & Canada) 800-55-FORTH
FORTH Inc. +1 310-491-3356
5155 W. Rosecrans Ave. #1018 Fax: +1 310-978-9454
Hawthorne, CA 90250
http://www.forth.com

"Forth-based products and Services for real-time
applications since 1973."
==================================================

----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
For list command help, send subject "help" to swiftx-request_at_forth.com
Message archives are located at http://www.forth.com/archive/swiftx
----------------------------------------------------------------------
This list is a forum for SwiftX users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Sun Aug 10 2003 - 09:17:39 PDT