[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: org.xml.sax.ContentHandler conflicts with java.net.ContentHan dler
Elliotte Rusty Harold writes: > Even accepting that "import java.net.*" is bad form, doesn't > absolve us of the responsibility to avoid the problem in the first > place. Not completely absolved, granted, but if programmers use java.net.* they're really setting themselves up for this. What happens if the next Java release also contains a java.net.InputSource class (for example), or a java.net.Locator class? Will we have to put out revised a SAX3/Java just to change those names as well? All the best, David -- David Megginson david@m... http://www.megginson.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/threads.html ***************************************************************************
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|