On 2/3/11 7:13 AM, Mathias Gaunard wrote:
Doing anything non-trivial with Phoenix requires creating lazy functions beforehand (typically done at namespace scope). The fact that Phoenix itself bundles many lazy functions for any other container member and standard algorithm (for a total of 4,000 lines of code for that task alone) is testament to that; you can't really work with it otherwise.
If you unwrap the macros from Boost.Local, something like a Phoenix.function will emerge. So, why not just provide a phoenix macro to give you the same level of verbosity and the same level of debuggability and c++ syntax error handling? It is trivial to write such a macro in phoenix. Regards, -- Joel de Guzman http://www.boostpro.com http://spirit.sf.net