Closed GoogleCodeExporter closed 8 years ago
The root of the problem is that XPath specification does not treat numbers as
locale-specific (so your request, while convenient in practice, violates
specification).
Introducing this feature silently will potentially break existing uses. And
there is currently no support for customizing query compilation (even if there
was, you'd have to use the new flag everywhere).
Finally, I'm reluctant to add yet another #define for this...
I'll think if I can introduce this feature without too many
interface/configuration changes.
Original comment by arseny.k...@gmail.com
on 6 Mar 2013 at 4:18
Unfortunately, there does not seem to be a good enough way to implement this as
an extra option. Also, in addition to other mentioned problems, this introduces
extra parsing ambiguities, i.e. substring("a",1,2) will be parsed in the
different way.
To summarize, the change is too problematic to be worth it.
Original comment by arseny.k...@gmail.com
on 10 Jul 2013 at 5:45
Original issue reported on code.google.com by
fer.fmat...@gmail.com
on 11 Feb 2013 at 10:05Attachments: