Re: Extension interfaces in SAX dot NET?

----- Original Message ----- 
From: "Elliotte Rusty Harold" <[email protected]>
To: "Karl Waclawek" <[email protected]>
Cc: <[email protected]>
Sent: Sunday, June 13, 2004 3:11 PM


> At 2:11 PM -0400 6/13/04, Karl Waclawek wrote:
> 
> >What would you then say about moving ILexicalHandler and
> >IDeclHandler into the core as well, or in other words,
> >eliminating the notion of core vs. extensions?
> 
> The problem with doing that is that it requires parsers to support 
> these extensions. If you're comfortable with that, OK, but it is 
> extra work for impleenters, especially at first. There's also an 
> extent to which these provide content that applications really 
> shouldn't rely on or use in a major way.

I undeerstand this point. My reason for asking was
basically that the same argument could be applied
to the IAttributes2, ILocator2 and IEntityResolver2
interfaces. So the question is: which extensions
really *are* extensions?

Karl




-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
List: sax-devel, [email protected]
See:  http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel