• From: Jim Layer <JBLayer@n...>
• To: xml-dev@x...
• Date: 2 Mar 00 17:30:48 EST

David Megginson <david@m...> wrote:

> > Suggestion. Retain the name and document the potential conflict in the
> > interface. 

> Suggestion accepted -- I've added it to the TODO list.

Might want to caveat rather generally as conflicts abound where naive or
undisciplined are concerned. Try something like

import org.xml.sax.*;
import oracle.xml.parser.v2.*;

...   

if (parser instanceof XMLReader)

...

and JDK V1.2.2 snarfs with an ambiguious reference error.  This despite the
fact that oracle.xml.parser.v2.XMLReader is a non-public. Let us not even get
into all of the *public* Parser, XMLParser, SAXParser, and similar classes in
parser land alone.

Although the conflict with java.net.ContentHandler is unfortunate, the thought
of a developer (building something involving XML parsers and java.net for
public release) who can't recognize and resolve the error in under a minute or
so - now *that's* unfortunate. ;)

Regards,

Jim Layer 

____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************

• Prev by Date: Re: The RDF model *is* part of the problem
• Next by Date: Structured attributes
• Previous by thread: Style of import declarations (Was: org.xml.sax.ContentHandler conflicts with java.net.ContentHandler)
• Next by thread: Fwd: Namespaces FAQ
• Index(es):
  • Date
  • Thread