Basically, you either override a method in one of the parsers, to get limited access to the scanner output, or you write your own parser style class and and store whatever you want, or you use the scanner directly within your application. If you look at something like the ParserTest program, you can see how that is done, or of course if you look at SAXParser or DOMParser they also are examples of how to interact with the scanner.
-------------------------- 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: "Jason E. Stewart" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, October 27, 2001 7:46 AM Subject: Re: Telling two empty tags apart > "Dean Roddey" <[EMAIL PROTECTED]> writes: > > > Its been a long time since I did it, but I think I put in code so > > that the underlying scanner reports the difference. But the problem > > is that it does not propogate out through any standard APIs. If you > > wanted to keep this info, you'd have to use the scanner directly and > > have your own data structures to put all the data in. > > Hey Dean, > > None of this is documented in the API docs (since it's not in the API) > how does what get ahold of the scanner? Do you have to monitor the > scanner during operation or is the information still around after the > parse is completed? > > Cheers, > jas. > > --------------------------------------------------------------------- > 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]
