Small remark:
Global objects seem to get out of fashion: They have a negative impact on
compile times and binary size.
instead of using phoenix::function on global (namespace) scope, you could use
the newly introduced macros to define equivalent free functions.
For example, instead of this:
On Monday, May 09, 2011 11:18:50 PM Christophe Henry wrote:
Hi,
Thanks to Eric's latest changes (which removed conflicts between MSM
and phoenix), and Thomas' help, I added the possibility to use phoenix
as an action inside eUML.
There is still quite a bit to be done to be able to do with
