Re: [boost] active objects implementation request for comments

On Monday 12 March 2007 06:42 pm, Braddock Gaskill wrote:

In libpoet's case (and I've only just started looking at it), you might be able to mitigate this somewhat if you check any future<T> arguments for an active_function invocation within a default guard. ie, the default guard for libpoet checks that all future<T> arguments are ready before running the active_function.

Yes, I probably neglected to document it, but the poet::active_function always logically ands the ready state of all it's input futures with any guard function you specify. So by default, the method request is ready to run and can be scheduled when all the inputs are ready. -- Frank