My code is pretty much backwards compatible - there have not been any striking semantic changes and all testcases pass on gcc 3.4/4.4 and vc 9. Unfortunately I have not had the time to put the code up for review yet. I am pretty positive that the code is trunk-ready though, and I will try to post a report on my work within the next days. Either way, for now you can workaround your issue by providing your own extension implementations for fusion::extension::category_of_implfusion::joint_view_tag, fusion::extension::has_key_implfusion::joint_view_tag and fusion::extension::at_key_implfusion::joint_view_tag, or, even better, wrap the joint_view up in another view which implements both (forward and associative) extension backends. -Christopher er schrieb:
I guess it wouldn't be a good idea for me to mix files from c++0x-port and boost.