• To: <xml-dev@l...>
• Subject: Re: SAX Locator vs {start,end}Entity
• From: "Karl Waclawek" <karl@w...>
• Date: Thu, 20 Feb 2003 13:12:15 -0500
• References: <200302201708.RAA24264@m...>

> >But why can't you achieve that by looking at the systemId() of the
> >Locator when startElement is called?
> 
> I could keep a stack of the locator's system ID for all elements, and
> compare it with the top of stack for each element - if it's different,
> there must have been an entity boundary - but it would be more
> efficient to notice start and endElement events.  It looks as if it
> will be best to notice the events, but delay finding the system ID
> until an element start occurs.

Why not store the entity declarations in a hash table, hashed by name?

Karl

• Follow-Ups:
  • Re: SAX Locator vs {start,end}Entity
    • From: Richard Tobin <richard@c...>

• References:
  • Re: SAX Locator vs {start,end}Entity
    • From: Richard Tobin <richard@c...>

• Prev by Date: Re: data input to an XSL produced page -- best practices
• Next by Date: Re: SAX Locator vs {start,end}Entity
• Previous by thread: Re: SAX Locator vs {start,end}Entity
• Next by thread: Re: SAX Locator vs {start,end}Entity
• Index(es):
  • Date
  • Thread