> >I am also assuming that we will provide not only a callback interface,
> >but also an (optional) base class with stub methods that implementors
> >can override as needed; that means that novice users will not have to
> >implement all of SAX, even if we do end up with nine or ten methods.
>
> This worries me. My interest is in implementations of SAX-clients in C++.
> Will I have, as part of somebody's SAX implementation that I'm using, this
> (optional) base class available to me too?
In C++ I can't see any need for a base class separate from the
interface. You can just have a single class which provides empty
definitions for all virtual functions.
James