• From: Matt Sergeant <matt@s...>
• To: Kay Michael <Michael.Kay@i...>
• Date: Fri, 30 Jun 2000 11:30:11 +0100 (BST)

On Fri, 30 Jun 2000, Kay Michael wrote:

> > Somebody says XPATH provide a better functionality than xql.
> > I am not sure about this. But lack of functions such as "like"
> > to compare strings, and nested condition (i.e. a [] inside a [])
> > makes it difficult to select some specified nodes with XPATH. 
> > One can make
> > extensions to XSLTs to overcome some of them (such as string 
> > A like string
> > B), but not always. Why don't the XPATH, allow using of 
> > nested conditions?
> >
> I suspect the absence of a "like" function in version 1.0 is because people
> didn't want to put regular expression matching in unless they got it right,
> which with full Unicode and full internationalisation is not actually easy.

FWIW I believe that some of the latest Unicode documentation references
Perl 5.6's regular expression extensions for Unicode (it might not be a
direct reference though).

Disclaimer: I've not read the Unicode docs in question.

-- 
<Matt/>

Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org | AxKit: http://axkit.org


***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************

• References:
  • RE: xpath vs xql
    • From: Kay Michael <Michael.Kay@i...>

• Prev by Date: RE: Saxon "PreparedStylesheet" problem
• Next by Date: RE: deterministic content model
• Previous by thread: RE: xpath vs xql
• Next by thread: helpful xpath utilities (for IE)
• Index(es):
  • Date
  • Thread