-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 16 May 2008 05:23 am, Johan Torp wrote:
Frank Mori Hess wrote:
Ah, yes it seems like some kind of composable future_switch and future_barrier could work quite well for my use case. Do they actually need to be classes though? What if they were just free functions for example
future<void> future_barrier(const future<void> &a1, const future<void>& a2, ... , const future<void> &aN);
If we want to support dynamically adding futures to future_switch and maybe future_barrier a free function won't suffice.
Yes, you're right. Especially with future_switch there should be a way to wait on a group of futures whose number is only known at runtime. - -- Frank -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFILZby5vihyNWuA4URAhChAJ9MTK+2ZoKBm8PVaoZZB5UqLHbeqACg5Xtm aPId2WGfrUTXhKdZbJjTYGo= =//EW -----END PGP SIGNATURE-----