Lists Home |
Date Index |
- From: David Megginson <email@example.com>
- To: "XML Developers' List" <firstname.lastname@example.org>
- Date: Wed, 17 Mar 1999 16:15:11 -0500 (EST)
Ronald Bourret writes:
> David Megginson wrote:
> > So far, for consistency, I've made all pre-parse properties
> > write-only and all parse-time properties read-only. We'll have
> > to think about this one.
> What is the possible benefit of making any property write-only?
> That is, can any harm ever come from reading a property?
There are three benefits:
1. Keep the API absolutely as small as possible.
2. Avoid confusion.
3. Allow properties to be unknown until set.
Any attempt to access a property can generate a
SAXNotSupportedException (or the derived SAXNotRecognizedException),
but there is no guarantee that they will be symmetrical. For example,
a driver built on top of a parser might allow you to set the namespace
separator but not to query it, or vice-versa.
All the best,
David Megginson email@example.com
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)