SAX: finalising org.sax.xml.Parser

James Clark jjc at jclark.com
Tue Feb 24 04:02:06 GMT 1998


>    public void parse (InputStream is, String baseURI)
>      throws java.lang.Exception;
>    public void parse (char ch[], int start, int length, String baseURI)
>      throws java.lang.Exception;

I don't think this last one is a good idea.  If you want something that
operates on a stream of characters as opposed to bytes, it should be

  void parse(Reader r, String baseURI)

Using an array of chars is as bad an idea as it would be to replace the
InputStream method with a method that operates on an array of bytes.

I am not convinced this really buys you anything.  It's easy enough to
write an InputStream that takes an array of chars and presents then as a
sequence of UTF-16 encoded bytes.  It also raise some problems since the
XML spec doesn't define the operation of a processor on an sequence of
chars.  For example, what if anything should the processor do with an
encoding declaration in this case?

If you don't want to put Readerin to avoid dependency on JDK 1.1, I
would suggest simply leaving this out for now.

James


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)




More information about the Xml-dev mailing list