28 Aug
2006
28 Aug
'06
6:59 a.m.
Andreas Huber wrote:
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.
Out of curiosity, why would one ever want to call scheduler::operator() before initiate_processor()? // Johan