id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
9742	for_each causes funny behavior in phoenix V3 expressions	Chromatix	Thomas Heller	"Using phoenix::for_each in a Phoenix expression produces a strange behavior, which seems to be reverse execution of the comma-separated expressions.
This does NOT happen when you include Phoenix V2 from the spirit directory.

Sample Code: (Full code attached)


{{{
std::vector<int> v{1,2};
(std::cout << phx::val(""(""),  phx::for_each(arg1, phx::lambda[std::cout << arg1]), std::cout << phx::val("")""))(v);
}}}


This originally showed up for me when using phoenix expressions in spirit semantic actions, discussed here: 
http://boost.2283326.n4.nabble.com/Phoenix-V3-for-each-or-lambda-seem-to-be-ruining-qi-semantic-actions-tp4659691.html"	Bugs	new	To Be Determined	phoenix	Boost 1.54.0	Problem		phoenix,for_each,lazy