|
Boost Users : |
From: Andreas Huber (ahd6974-spamgroupstrap_at_[hidden])
Date: 2006-08-26 01:36:23
Johan Nilsson wrote:
[snip]
> Well, isn't it weird that as soon as one asks for help, you find the
> problem yourself.
>
> I'd just forgot the call to fifo_scheduler<>::initiate_processor in
> the application. Doh!
>
> Would it be possible to check if the processor has been initiated when
> calling "scheduler::operator()"?
The current interface allows you to create and initiate processors
before or after scheduler::operator() has been called. Sometimes you
even need to call create_processor() before and initiate_processor()
afterwards. Sometimes you also want to reuse a state_machine that has
terminated and therefore need to call initiate_processor() again.
Therefore, if scheduler::operator() asserts that all created processors
have also been initiated then this would preclude some legitimate
real-world use cases and would also not catch the cases where a FSM has
terminated after being initiated.
Regards,
-- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net