[mailto:boost-bounces@lists.boost.org]On Behalf Of Matthew Vogt
nice! only one item of feedback really. think that i follow your machinery and can envisage the "model of execution" - its pretty slick. its also somewhat different to the pattern :-| so i would wonder at the use of "active object"? is your model of execution the one that everyone is expecting of the previously, unimplemented class? this does seem to be a class/framework for (very convenient) arrangement of concurrent method execution. which piece of the ActiveObject pattern does this map to? other than the "claiming of the name", it looks like its got legs! ps: i s'pose anything declared in the private scope of "object" is thread safe?
// test_active_object.cpp --------------------------------------------------
#include "active_object.hpp"
using std::cin; using std::endl;
<big snip>