Hi Roger. I may be misunderstanding your question, but I think the answer is that OrExpr recurses down PathExpr. You can follow the recursion basically by clicking on the first member of the right hand side of the BNF productions. This particular cascade is what implements the built-in precedence. Anyway, I believe the BNF to be correct, and the structure, dumped from the diagnostics of the test parser, is: |XPath | Expr | QuantifiedExpr | Every every $ | VarName part | In in | PathExpr | RootDescendants // | StepExpr | NodeTest | NameTest | QName part | Satisfies satisfies | PathExpr | VarName part | StepExpr | At @ | NodeTest | NameTest | QName discounted Note that the test parser reduces many of the unneeded steps, for instance for ExprSingle to PathExpr, as I think you would for most ASTs. -scottReceived on Thursday, 29 January 2004 16:21:32 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:04 GMT