Hi,
I have a small issue which puzzles me a little.
I want to provide my DSEL a syntax very much like the map_list_of example:
func( some_grammar_expr )..; //extra parens coming later = func(
some_grammar_expr )( some_other_grammar_expr )
which I would like to generate me a functor object. I have
On 7/27/2010 8:48 AM, Christophe Henry wrote:
Hi,
I have a small issue which puzzles me a little.
I want to provide my DSEL a syntax very much like the map_list_of example:
func( some_grammar_expr )..; //extra parens coming later = func(
some_grammar_expr )( some_other_grammar_expr )
which
On 7/27/2010 9:01 AM, joel falcou wrote:
what about having some Tree related trasnform/function/meta-function then ?
I'm often thinking : dang, this transform is basically a BFS for a node
verifying meta-function foo
and have to rewrite a BFS usign default_ and such, which is relatively
On 27/07/10 15:08, Eric Niebler wrote:
That would be awesome, Joel!
I'll count on you for helping me making those looking nice :p
What's the easiest ? getting a proto-tree branch or what ?
___
proto mailing list
proto@lists.boost.org
what about having some Tree related trasnform/function/meta-function then ?
I'm often thinking : dang, this transform is basically a BFS for a node
verifying meta-function foo
and have to rewrite a BFS usign default_ and such, which is relatively easy.
Now, sometimes it is dang, this code is
On 27/07/10 15:08, Eric Niebler wrote:
That would be awesome, Joel!
WHat's the easiest in term of code ?
I can bring up some git repo or shoudl I work in some svn branches of
proto somewhere at boost ?
___
proto mailing list
I think you should talk to Gordon Woodhull. He's building a metagraph
(among others) library, which I am going to use in msm for
compile-time calculations and fsm analysis. This means there will be
temporarily a metagraph library inside msm as proof of concept until
there can be a review.
