May 26, 2006
2:39 p.m.
Tres Seaver wrote:
Honestly, unless there are good reasons to do it, I'm absolutely +1 for keeping the current state.
Agreed, this is a no broainer. If your application needs to be compatible with ET/cET, use the compatibility API. If it needs full XPath support, then use the native XPath API.
and as usual, if someone finds a glaring difference between how findall handles a given xpath pattern and how xpath handles it (clarke notation issues aside), it's probably a bug in ET. </F>