[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Nasty XPath expressions

• To: Kelvin Yeow <whyeow@c...>
• Subject: Re: Nasty XPath expressions
• From: Daniel Veillard <veillard@r...>
• Date: Thu, 13 Dec 2001 12:06:19 -0500
• Cc: xml-dev@l...
• In-reply-to: <Pine.SUN.3.96.1011213023431.6142C-100000@valdes>; from whyeow@c... on Thu, Dec 13, 2001 at 02:41:39AM -0800
• References: <Pine.SUN.3.96.1011213023431.6142C-100000@valdes>
• Reply-to: veillard@r...
• User-agent: Mutt/1.2.5i

On Thu, Dec 13, 2001 at 02:41:39AM -0800, Kelvin Yeow wrote:
> I wonder what XPath expressions would cause an "XPath processor" to sweat?
> Any "XPath processor" developer out there?

  Of course expressions requiring to browse the full tree are a real
pain from an implementor point of view (or rather an implementor willing to
get decent speed out of the engine).
  But the main problem is IMHO addressing namespaced nodes especially 
when the context don't allow the user to use a QName (like nodes in
the default namespace):

   //*[local-name()="body" and namespace-uri()="http://www.w3.org/1999/xhtml"]

 This is both:
   - horrible to find out and use by users
   - horrible to evaluate at run-time

Daniel

-- 
Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard@r...  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

• References:
  • Nasty XPath expressions
    • From: Kelvin Yeow <whyeow@c...>

• Prev by Date: RE: Nasty XPath expressions
• Next by Date: Re: Nasty XPath expressions
• Previous by thread: RE: Nasty XPath expressions
• Next by thread: [OT] Test
• Index(es):
  • Date
  • Thread