The only advantage I see for having a language-neutral SAX is having a
parser, say written in C, called from a client written, say in Java,
all in the same machine (and probably the same process).
There are not that many pairs of interest (to me, I'm a Java
programmer), so I'd *much rather* put the burden on the implementor of
the parser, or of the translation layer, than on the client.
I.e. I'd *much rather* have a SAX/Java that mix best with Java than
a language-neutral SAX.
Of course, it depends on what your goals are.
- eduardo