[Home] [By Thread] [By Date] [Recent Entries]
This would force the use of fully qualified names and create name conflicts for programmers used to simply importing the classes being used. I try hard to avoid such potential name conflicts and would prefer XParser, ExParser, Parser2, ModParser, OpenParser, or anything else over Parser. Bill -----Original Message----- From: John Cowan <cowan@l...> To: xml-dev@i... <xml-dev@i...> Date: Saturday, March 13, 1999 3:24 PM Subject: Re: Are we ready to resolve the Mod??SAX name? >Bill la Forge scripsit: >> >> Should we just stick with ModSAX/ModParser? >> Should we change to OpenSAX/OpenParser? > >I support OpenSAX/Parser, in other words keeping the names of the >classes and interfaces the same, and changing the package name only. > >-- >John Cowan cowan@c... > e'osai ko sarji la lojban. > >xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... >Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 >To (un)subscribe, mailto:majordomo@i... the following message; >(un)subscribe xml-dev >To subscribe to the digests, mailto:majordomo@i... the following message; >subscribe xml-dev-digest >List coordinator, Henry Rzepa (mailto:rzepa@i...) > xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|

Cart



