Something to consider: Xerces' C++ namespace is conditional, because in the past some compilers have lacked namespace support. This situation is presumably improving over time; has it gotten to the point where namespace support can be assumed?
The only opinion I have to offer is that consistency in naming is a good idea. It helps make relationships among classes clear, especially for new users. Prefixing some DOM-related classes with "DOM" and leaving the prefix off others sounds confusing. Note that I'm talking without any real knowledge of the API Gareth is implementing, so consistency may not be of as much value as I'm assuming, in which case the rest of this message is irrelevant. I can see a couple of choices. If namespace support is sufficiently widespread (whatever that means), we can: - consistently use the "DOM" prefix, - or consistently omit it (which breaks all existing code). If compilers without namespace support are still too common, the former approach remains preferable. > -----Original Message----- > From: Gareth Reakes [mailto:[EMAIL PROTECTED] > Sent: Monday, August 18, 2003 12:34 PM > To: [EMAIL PROTECTED] > Subject: Level 3 XPath interfaces > > > Hi all, > > I am currently writing the XPath Level 3 interfaces. This is on > the road map for eventual inclusion of Pathan into xerces. > > I am looking for opinions on the naming of these > classes. In the > past we have prefixed DOM interfaces with "DOM" (eg > DOMDocument). We have > primarily done this due to the possibility of name clashes. This > is no longer a problem because of namespace support. So, does anyone > have a preference for DOMXPath... (eg DOMXPathNSResolver) > which will at > be consistent, or XPath... (XPathNSResolver) which prevents that > irritating lack of ability to tab complete and prettier filenames? > > My preference is for XPath... and Neils is for DOMXPath... but > neither of us have particularly strong opinions. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
