This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Why is RelationalExpr left associative?


Dear XPath experts,

can anyone give me the reason why the productions for EqualityExpr 
and RelationalExpr have been designed the way they are?
(See http://www.w3.org/TR/xpath#NT-RelationalExpr )
The note in the specification about 3 > 2 > 1 talks about a possible 
misinterpretation.
So the question is: why are these kinds of expressions allowed? Are 
there any useful situations in which one can benefit?

I think formulating the production for RelationalExpr to be
nonassociative like this

RelationalExpr ::= AdditiveExpr
                   | AdditiveExpr '<' AdditiveExpr
                   | AdditiveExpr '>' AdditiveExpr
                   | AdditiveExpr '<=' AdditiveExpr
                   | AdditiveExpr '>=' AdditiveExpr

would avoid such "nonsense" 3 > 2 > 1 expressions.

(Dito for EqualityExpr and the example 0 = 0 = 0).

Thanks for giving me any insights :-)
Cheers,
Oliver

/-------------------------------------------------------------------\
|  ob|do        Dipl.Inf. Oliver Becker                             |
|  --+--        E-Mail: obecker@informatik.hu-berlin.de             |
|  op|qo        WWW:    http://www.informatik.hu-berlin.de/~obecker |
\-------------------------------------------------------------------/

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]