W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2009

[Bug 7999] [XPath 2.0] Leading lone slash, and (/+5), (/-5)

From: <bugzilla@wiggum.w3.org>
Date: Thu, 22 Oct 2009 14:27:39 +0000
To: public-qt-comments@w3.org
Message-Id: <E1N0ydf-0002YP-Ol@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7999


Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #1 from Michael Kay <mike@saxonica.com>  2009-10-22 14:27:38 ---
I've looked more carefully at the grammar, and it seems this is not a problem,
because unary plus and unary minus cannot appear at the start of a
RelativePathExpr.

An expression that isallowed at the start of a RelativePathExpr must be either
an AxisStep or a PrimaryExpr. AxisStep includes various forms of wildcard as
well as ".." and "@xx". PrimaryExpr includes literals, function calls,
parenthesized expressions, ".", variable references, ordered{} and unordered{},
and direct and computed node constructors. It doesn't include unary plus or
minus, conditional expressions, FLOWR expressions, validate expressions,
pragmas, or various other things that could be parsed without ambiguity in such
a context if we chose to allow them.

It seems pretty arbitrary what's allowed and what isn't, and I made the mistake
of assuming that any unary operator would have higher precedence than an infix
binary operator, but it doesn't, so this problem doesn't exist. I'm closing it
as INVALID.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 22 October 2009 14:27:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:41 UTC