• To: "Christian Nentwich" <c.nentwich@c...>,"Michael Brennan" <Michael_Brennan@A...>
• Subject: Re: Nasty XPath expressions
• From: "Dare Obasanjo" <kpako@y...>
• Date: Fri, 14 Dec 2001 08:42:58 -0800
• Cc: <michael.h.kay@n...>,"'bob mcwhirter'" <bob@w...>,"'Kelvin Yeow'" <whyeow@c...>,<xml-dev@l...>
• References: <D7155AD41ECFD511AF4A00B0D0202CB51DFB51@MAILHOST> <1008336477.1200.3.camel@w...>

----- Original Message -----
From: "Christian Nentwich" <c.nentwich@c...>
To: "Michael Brennan" <Michael_Brennan@A...>
Cc: <michael.h.kay@n...>; "'bob mcwhirter'" <bob@w...>; "'Kelvin
Yeow'" <whyeow@c...>; <xml-dev@l...>
Sent: Friday, December 14, 2001 5:27 AM
Subject: RE:  Nasty XPath expressions

>
> I won't even start with my success of binding my own variables in the
> .NET System.Xml classes. Their System.Xml.XPath classes do not even
> envisage that someone might ever want to do this.. you have to pick out
> Xsl classes, and then the exceptions start...
>

If you don't mind me asking, what problems have you had?

> A couple of use cases for the XPath specifications could have prevented
> this mess.
>

Agreed.

--
THINGS TO DO IF I BECOME AN EVIL OVERLORD #136
If I build a bomb, I will simply remember which wire to cut if it has to
 be deactivated and make every wire red.


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

• Follow-Ups:
  • xpath mess case study: .net (was: Nasty XPath expressions)
    • From: Christian Nentwich <c.nentwich@c...>

• References:
  • RE: Nasty XPath expressions
    • From: Michael Brennan <Michael_Brennan@A...>
  • RE: Nasty XPath expressions
    • From: Christian Nentwich <c.nentwich@c...>

• Prev by Date: RE: Nasty XPath expressions
• Next by Date: Re: First XML-1.1 Working Draft publicly available
• Previous by thread: RE: Nasty XPath expressions
• Next by thread: xpath mess case study: .net (was: Nasty XPath expressions)
• Index(es):
  • Date
  • Thread