I will create the SAX based C++ printers, which will be pretty much a straight
port from Assaf's code. Given time I might write the DOM printer that sits on
top of the SAX one, but that will come later.

--Keith

Assaf Arkin wrote:

> Mike Pogue wrote:
> >
> > Hey, Arkin...can we get a C++ version, too, so that the two
> > Xerces parsers stay together?  I'd expect that the Java and
> > C++ Xerces parsers would want to serialize and canonicalize
> > identically.
>
> The Java code can be migrated into C++, but I'll have to decline this
> one, I haven't written a line of C++ in nearly three years, and it's
> hard to get back.
>
> arkin
>
> >
> > Mike
> >
> > Assaf Arkin wrote:
> > >
> > > OK. Package name changes to org.apache.xerces.serialize
> > >
> > > arkin
> > >
> > > Tom Palmer wrote:
> > > >
> > > > > people confuse because Java semantics are a bit different and more
> > > > > common.
> > > > >
> > > > The trick is having to cope with two groups using the same
> > > > word in slightly different ways, and any name picked that is
> > > > nice for Java may end up being bad for another language.
> > > >
> > > > It would be good to use the terms that the W3C uses.
> > > >
> > > > Adding a qualifier may help at times: DOM serialization vs.
> > > > Java serialization.  Of course, this would only be useful for
> > > > normal conversation and so on.  Package naming is a
> > > > different issue.
> > > >
> > > > - Tom Palmer
> > >
> > > --
> > > ____________________________________________________________
> > > Assaf Arkin                               [EMAIL PROTECTED]
> > > CTO                                  http://www.exoffice.com
> > > Exoffice, The ExoLab Company             tel: (650) 259-9796
>
> --
> ____________________________________________________________
> Assaf Arkin                               [EMAIL PROTECTED]
> CTO                                  http://www.exoffice.com
> Exoffice, The ExoLab Company             tel: (650) 259-9796

Reply via email to