Thanks for copying me; I don't seem to be subscribed to general.,, >So are you saying you prefer the following option? > + Optimize for #2 (less code duplication) >From a code cleanliness/robustness/extensibility point of view, yes, I think so. But I recognize that there are convenience issues which will cause folks to feel otherwise; it's one more opportunity for users to botch their classpaths. On the other hand, given how often we have to explain to them that the ordering of the classpath may implicitly affect which level of the DOM they see, maybe making this explicit would be a good thing. It does mean buying ourselves a short-term reeducation effort, though. ______________________________________ Joe Kesselman / IBM Research --------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
- xml-commons XML API and API evolution Edwin Goei
- Re: xml-commons XML API and API evolution jean-guillaume . battaglia
- Re: xml-commons XML API and API evolution Shane_Curcuru
- Re: xml-commons XML API and API evolut... Edwin Goei
- xml-commons XML API and API evolution Joseph Kesselman
- Re: xml-commons XML API and API evolut... Edwin Goei
- Re: xml-commons XML API and API evolution Scott_Boag
- Re: xml-commons XML API and API evolut... Edwin Goei
- Re: xml-commons XML API and API evolution Joseph Kesselman
- Re: xml-commons XML API and API evolution Scott_Boag
- Re: xml-commons XML API and API evolut... Edwin Goei
- Re: xml-commons XML API and API evolution Joseph Kesselman
- Re: xml-commons XML API and API evolution Edwin Goei
- partial parsing of XML Andrew Anand
- Re: xml-commons XML API and API evolution Ben Coman
- Re: xml-commons XML API and API evolut... Edwin Goei
- RE: xml-commons XML API and API evolution Robert Stuart
- RE: xml-commons XML API and API evolut... Alistair Hopkins