[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: SAX and Entity Literals containing content

• To: Rick Marshall <rjm@z...>
• Subject: Re: SAX and Entity Literals containing content
• From: Bob Foster <bob@o...>
• Date: Tue, 25 May 2004 20:59:22 -0500
• Cc: xml-dev@l...
• In-reply-to: <40B3D869.8040101@z...>
• References: <030f01c44266$1252f320$6403a8c0@ARIMATHEA> <p06010202bcd91e1e005e@[192.168.254.88]> <40B3CBE1.8060403@z...> <001701c442ad$d6d671d0$0300a8c0@karlglen188> <40B3D869.8040101@z...>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

Rick Marshall wrote:
>>> so is this perfectly ok?
>>>
>>> <!DOCTYPE doc [
>>>  <!ENTITY e "<foo>">
>>> ]>
>>> <doc>
>>>  <child>&e;test</foo></child>
>>> </doc>

[No from several people.]

> fair enough, but it does seem to me it's being parsed twice - once to 
> make sure it's ok as an entity and once again when it's substituted. no 
> doubt this appeals to neatness, but it does seem excessive, and perhaps 
> restrictive. but that debate has no doubt been had and i don't want to 
> open it again.

Not much danger of that. ;-}

If you know what the parser is supposed to be checking, you can write 
the parser so it's convenient to check it. The simplest thing, perhaps, 
is to note the element nesting level at the beginning of the expansion 
and verify it's the same at the end.

Bob Foster

• References:
  • SAX and Entity Literals containing content
    • From: "Jeff Rafter" <lists@j...>
  • Re: SAX and Entity Literals containing content
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: SAX and Entity Literals containing content
    • From: Rick Marshall <rjm@z...>
  • Re: SAX and Entity Literals containing content
    • From: "Karl Waclawek" <karl@w...>
  • Re: SAX and Entity Literals containing content
    • From: Rick Marshall <rjm@z...>

• Prev by Date: Re: SAX and Entity Literals containing content
• Next by Date: Java classes - XML schema mapping
• Previous by thread: Re: SAX and Entity Literals containing content
• Next by thread: Re: SAX and Entity Literals containing content
• Index(es):
  • Date
  • Thread