Hi Yigong,
it. However one important feature of Boost.Join is to allow applications to create a vector of async / synch methods which will be prohibited by noncopyable.
Any suggestions?
The oldest solution in C/C++; pointers to? eg; vector<async<...> *> smart_ptrs? I can also vaguely guess why you would want vectors of async/synch but vectors of actor? Isnt it a base and therefore vectors of base would involve slicing? Don't fully understand the problem space so I wont be embarrassed if these are ignored. Still learning Join. Its going to take a while. At language level it's quite simple but the underlying model is less so and is "outside the box". The best I can do at the moment is try to translate the examples into SDL. For reasons I have not truly clarified this translation is only successful in one direction, i.e. Join -> SDL. I suspect that the systems expressible in SDL may be a superset of those expressable in Join. Or more Join-based code is required to support the more complex SDL systems. Its a bit of a struggle and I dont know that the comparison is even valid. Cheers.