Yes, as I said in an earlier message, if you use the scanner directly, you can get this info. As you point out, you can override just the start element and avoid writing your own parser, but you must store this information yourself.
-------------------------- Dean Roddey The Charmed Quark Controller Charmed Quark Software [EMAIL PROTECTED] http://www.charmedquark.com "If it don't have a control port, don't buy it!" ----- Original Message ----- From: "Peter A. Volchek" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 26, 2001 9:02 AM Subject: Re: Telling two empty tags apart > ----- Original Message ----- > From: "Dean Roddey" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, October 26, 2001 11:01 > Subject: Re: Telling two empty tags apart > > > > They are completely identical from XML's point of view, therefore they are > > from the parser's point of view. If what you are looking for is to print > > them back out the same as how they were seen originally, you couldn't do > > that. > > What about to provide own parser class with overridden method startElement() > ? > It has an argument "const bool isEmpty" which set to true when <A/> is > parsed, > meaning than there would be no endElement() call. > So, the user may store such an elements in his own pool, and then, when > printing DOM tree, prints the element from pool as <A/> and others as > usually <A></A> > Thoughts ? > > Peter A. Volchek > Software Engineer > Metis International, Inc. > [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
