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

Re: genx - genxEndTag

• To: "xml-dev mailing list" <xml-dev@l...>,"Tim Bray" <tbray@t...>
• Subject: Re: genx - genxEndTag
• From: "Karl Waclawek" <karl@w...>
• Date: Thu, 22 Jan 2004 11:13:31 -0500
• References: <0806139A-4C8A-11D8-905C-000A95A51C9E@t...> <007901c3e0f7$7d81fa40$9e539696@citkwaclaww2k>

One more thing I just thought about - reading your online
essay where one item to check for was "detecting misnested tags".

Now genxEndTag does not have name/prefix/uri arguments, which
it does not need to, as you just write out the next name
popped from your internal stack. 

I use the same approach in my own writer implementation,
however, I found it hard to debug, as you only find out
at the end when there are too few (or too many) genxEndTag calls.
(in my case "too few" doesn't happen, as - for convenience - the 
implementation adds missing end tags when the writer is closed).

It also makes it harder to write valid XML, since a misplaced
genxEndTag will not normally lead to malformed XML which
could be detected, but it will change the structure in an
un-intentioned way.

Just so that the programmers intention is more clearly
expressed it might worth thinking about adding the
name/prefix/uri arguments to the genxEndTag call.

Karl

• Follow-Ups:
  • Re: genx - genxEndTag
    • From: Tim Bray <tbray@t...>

• References:
  • genx - consensus items
    • From: Tim Bray <tbray@t...>
  • Re: genx - consensus items
    • From: "Karl Waclawek" <karl@w...>

• Prev by Date: Re: XLink and mixed vocabulary design
• Next by Date: Re: XLink and mixed vocabulary design
• Previous by thread: Re: genx - consensus items
• Next by thread: Re: genx - genxEndTag
• Index(es):
  • Date
  • Thread