-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stefan Behnel 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. I can't even see why we are talking about changing such a simple story. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEdt/2+gerLs4ltQ4RAty4AKCv9lO7gmPWxO/Hmwk1JO/LlUjwTwCePFJf tDQN3pHsqCDrziVmmx5UBTI= =HRhp -----END PGP SIGNATURE-----