Re: The correct code

Hi,

>One technique that I've used during development is keep the <taskname>
>ACTIVATE words together and rather than include ACTIVATE in the task
>itself. This allows me to test my routines on the console (or in the main
>terminal task). This way I don't have to modify the words to use them as
>tasks. In your working code, you would make these small changes:
>
>: SEQBITFLASH BEGIN PAUSE ... code ... AGAIN ;
>
>After this is done, this action can be assigned to a TASK, so:

>TASK ACTIVATE SEQBITFLASH
>
>Its a small difference but makes clearer that SEQBITFLASH is a task started
>with the name TASK. In function, yours is identical and works perfectly.
>Its just a readability issue.

What an excellent idea. It makes it all even more flexible, indeed.
Luckily I have such a problem from time to time - it
keeps Forth somewhat difficult and one learns
even more finnesses.

Thanks.
Viviane
----------------------------------------------------------------------
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 Mon Aug 11 2003 - 08:45:38 PDT