Harold Hallikainen wrote:

> I'm wondering about maybe having a single fifo that is the input to all
> tasks. Any task would place messages in this fifo. When a task resumes,
> it would see if the first message in the fifo was for it. If not, it
> would exit and allow the next task to run, which would also check the
> first message in the fifo. Messages would be pulled off the fifo in
> order so we don't end up having to keep track of empty spaces in the
> fifo. This may result in the system locking up, but it SEEMS like as
> long as each task pulls a message off the fifo every time the task runs,
> it should work. The only time a task would exit would be when the first
> message in the fifo is NOT addressed to this task. So... that's my
> current thinking.

You may consider either a second high-priority FIFO (works the exactly the
same, but is only used for higher priority messages) or an accessor to the
queue that allows a task to place a message into the output end (giving it
so to speak a higher priority than all other messages in the queue).

Gerhard

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist