Lists Home |
Date Index |
- From: Toivo Lainevool <firstname.lastname@example.org>
- To: Ronald Bourret <email@example.com>, XML Developers' List <firstname.lastname@example.org>
- Date: Sat, 21 Nov 1998 09:55:17 -0800 (PST)
---Ronald Bourret <email@example.com> wrote:
> Patrice Bonhomme wrote:
> > I think there is a little problem with AttributeList implementation
> > some of the SAX drivers (i have tested the following code with my
> > driver, the XML4J SAX driver and the AELFRED SAX driver. We are all
> giving the
> > same results (gosh...).
> > This code should write the size of each AttributeList that has
> > the parser when it reached the end of the Document. But it always
> > size of the last AtributeList found.
> > [code snipped]
> It is a good bet that all the parsers are doing what I have done in
> parsers: used a single instance of an AttributeList object, then
> and reused it for each call to startElement. Thus, all the
> your Vector point to the same object.
> This is specifically allowed by the SAX spec. The documentation for
> AttributeList states, "The instance provided will return valid
> during the scope of the startElement invocation (to save it for
> the application must make a copy: the AttributeListImpl helper class
> provides a convenient constructor for doing so)."
Instead of clearing and reusing the the AttributeList object, wouldn't
it be better to create a new attribute list object? If the old
Attribute list isn't being referenced, it will be garbage collectible.
If the old Attribute list is being reference, it won't be changed out
from under the client. This way of doing it seems to offer the best
of both worlds.
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.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/
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)