At 09:12 PM 6/1/97 -0400, you wrote:

>Oh, yes, and that the multiple tasks communicate with one another, forcing
>them to idle or act upon a stimulus.
>
>Interrupts are not required - not pre-emptive.
>
>Also very easy to understand, as it is very deterministic.  Therefore
>rather easy to debug, document, etc.
>
>And efficient in both code and time.
>
The New Micros company has formalized that approach and called it
isostructure programming.  They're claiming to ship
a chip with the language they call ISOMAX burned in
soon, plus they'll offer c code generators for translating
to other than the controllers they do, for a price.

I'm planning to copy their/your style for my foundry
control project, since they are 68hc11 products mostly.
The cooperative MT/ISOMAX method skips having a
complicated, memory consuming RTOS to buy and pay
royalties on.  I like that.

New Micros has a paper on their site that's brief
http://www.newmicros.com/isomax.html, and
I got one in the mail that's more detailed.
Part of that is at my website at
http://www.tpoint.net/~john_g/FoundryNet/reprogrammable_method.html

John

John Griessen  CIBOLO Metal Works
3406 Hancock Dr Austin TX 78731-5432  512 451-8207 FAX 451-0753
http://www.tpoint.net/~john_g/cibolo/