Hi John, Another area where we can improvise the interface alignment is DOMXPathNSResolver. I just had a quick chat with Alberto and here are the changes that we both agree would make sense (I hope the motivation is self-evident, if not -- let me know):
1. Add the ability to provide custom namespace-prefix mappings in the DOMXPathNSResolver interface. Something along these lines: virtual void setNamespacePrefix (const XMLCh* prefix, const XMLCh* uri); The new mapping will override any existing one. If NULL or empty string is passed as uri then the existing mapping, if any, is removed. 2. Change the createNSResolver() function in DOMXPathEvaluator to return read-write DOMXPathNSResolver (const right now). 3. Allow NULL to be passed to createNSResolver() in which case empty DOMXPathNSResolver will be created (can then be populated with setNamespacePrefix). Let me know what you think. Boris -- Boris Kolpackov, Code Synthesis Tools http://codesynthesis.com/~boris/blog Open source XML data binding for C++: http://codesynthesis.com/products/xsd Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
