Thank you your example really helped me. I'm using the following as a test case: fdqfds dd d ^!for-each ( a/b/c()/e[]/d ) ( item ) Here are the rules { boost::spirit::chlit<> LPAREN('('); boost::spirit::chlit<> RPAREN(')'); boost::spirit::strlit<> CMDSWITCH("^!"); script = * ( (boost::spirit::anychar_p - CMDSWITCH) | command ); /* */ command = boost::spirit::discard_first_node_d[ CMDSWITCH >> (for_each | to_string | boost::spirit::eps_p [&calculator::error_log] ) ] ; /* */ for_each = boost::spirit::discard_first_node_d[ boost::spirit::as_lower_d["for-each"] >> *boost::spirit::space_p >> query >> *boost::spirit::space_p >> subscript ] ; /* */ query = boost::spirit::inner_node_d[ LPAREN >> * ( query_text1 | query_text2 ) >> RPAREN ] ; { // this is to handle balanced () inside query query_text1 = boost::spirit::anychar_p - (LPAREN|RPAREN); query_text2 = LPAREN >> * ( query_text1 | query_text2) >> RPAREN ; } subscript = boost::spirit::inner_node_d[ LPAREN >> *( command | subscript1 | subscript2 ) >> RPAREN ] ; { // this is to handle balanced () and command inside subscript subscript1 = boost::spirit::anychar_p - (CMDSWITCH|LPAREN|RPAREN) ; subscript2 = LPAREN >> *( subscript1 | subscript2 | command ) >> RPAREN ; } to_string = boost::spirit::as_lower_d["to-string"] ; } I'm building an tree while parsing and then I'm printing it using boost::spirit::tree_to_xml. I have 2 additional questions : 1) The for each statement produces the following AST. The nodes marked with XXX at end of lines are produced due to the "*boost::spirit::space_p " part of the for-each rule. Is there a way (a directive or something else in the grammar) to skip this content so that the marked nodes (XXX) would not appeared in the AST ? (i have tried discar_node_d, and other directives but nothing works) <parsenode rule="for_eachID"> <parsenode> XXX <value> </value> XXX </parsenode> XXX <parsenode rule="queryID"> <parsenode> ... </parsenode> </parsenode> <parsenode> XXX <value> </value> XXX </parsenode> XXX <parsenode> XXX <value>\n</value> XXX </parsenode> XXX <parsenode> XXX <value> </value> XXX </parsenode> XXX <parsenode rule="subscriptID"> <parsenode> ... </parsenode> </parsenode> </parsenode> 2)The query rule handles inner balanced parentheses but it produces the following AST: =>input is b/c()/e I Would like the AST produced from the inner () to be flatten. I would like the node marked with XXX not to be generated. Is there a directive for this ? <parsenode> <value>b</value> </parsenode> <parsenode> <value>/</value> </parsenode> <parsenode> <value>c</value> </parsenode> <parsenode> XXX <parsenode> <value>(</value> </parsenode> <parsenode> <value>)</value> </parsenode> </parsenode> XXX <parsenode> <value>/</value> </parsenode> <parsenode> <value>e</value> </parsenode>

is there any way to manage this with 1.6.4 My parser is part of a bigger project, I don't think I would be authorized to upgrade spirit (might have side effects). Moreover, I think there are issues with the compiler we use (BCC). I will try on my own computer outside of the project versionning system.

On Sun, Apr 18, 2010 at 3:34 AM, EricB wrote:

I have tried with latest version of spirit. I get "Compiler not supported."

Therefore I have to keep using 1.6.4.

Ah, BCC, yes, that compiler has a *ton* of issues, and that is still putting it mildly. Why is your place using such an absolutely broken compiler? Any chance of using GCC/MSVC?

EricB schrieb:

is there any way to manage this with 1.6.4

If only need to checked whether the string contains the same number of '(' and ')' what about int counter=0; rule<> r = ch_p('(')[increment_a(counter)] >> ~ch_p(')') >> ch_p(')')[decrement_a(counter)] if(counter!=0) { // unbalanced! } L.R.

On 4/20/2010 1:14 PM, OvermindDL1 wrote:

On Mon, Apr 19, 2010 at 8:22 AM, Lars Rohwedder wrote:

...

EricB schrieb:

...

is there any way to manage this with 1.6.4

If only need to checked whether the string contains the same number of '(' and ')' what about

int counter=0;

rule<> r = ch_p('(')[increment_a(counter)]>> ~ch_p(')')>> ch_p(')')[decrement_a(counter)]

if(counter!=0) { // unbalanced! }

Unnecessary, slower, and error-prone. There is still a 'raw' equivalent in Spirit1 as I recall, but I do not know the syntax, you

Spirit1 is always "raw" in the sense that it is basically a transduction parser and returns the iterators to the matching range in the input. Regards, -- Joel de Guzman http://www.boostpro.com http://spirit.sf.net http://www.facebook.com/djowel Meet me at BoostCon http://www.boostcon.com/home http://www.facebook.com/boostcon

On Wed, Apr 21, 2010 at 6:05 AM, EricB wrote:

I can not post on gmane.comp.parsers.spirit.general with firebird !!! Is there a specific way to post there

Gmane is a pain, never touch it, use the official Spirit mailing list: https://lists.sourceforge.net/lists/listinfo/spirit-general