On 14/03/11 04:49, Eric Niebler wrote:
Exciting stuff! Truly Christophe, your ideas re decltype and EDSLs in
C++ are revolutionary. But unfortunately, I fear it will require a
revolution. This is all do-able, but the changes to MPL, Proto and even
to Phoenix in the case of the lambda capture
On Monday, March 14, 2011 01:39:41 PM Christophe Henry wrote:
Hi Thomas,
Row source_state , event , target_state, action , guard
I suggest you to look into spirit how semantic actions are dealt with, it
reminds me of exactly this:
Ok I will, thanks.
Keep in mind, spirit uses Phoenix
Calling phoenix expressions from the statement module return void.
Calling phoenix expressions from any other modules return whatever ...
depending on the C++-Sense.
It's ok, I can live with it, though I'll need to find a way around
because I do need this return stuff.
If you allow a short
Hi Eric,
First let me say that I have limited bandwidth at the moment, and apologize in
advance for my short reply...
No need to apologize, I can understand this ;-)
And what you need is for the type of the Proto expression generated by
(g1 || g2) !g3 to be default-constructable? Have you
.. the talk from Matt Calabrese last year at boostcon with the
MPL/Fusion hybrid
using decltype and auto. I think this is an interesting venture all in
all and should
be extended.
Yes, I have this in mind too.
I have the same kind of ideas Christophe plus a few other (including a
real
