[email protected] wrote on 2009-08-20:
> 2) Is the migration path from Xerces-C 2.7.0 to Xerces-C 3.0.x difficult?

If you don't need to stay compatible with 2.x, it's not that painful (but
can be a bit of work). If you do, it's a fair amount of autoconf and ifdef
work, and in some cases requires defining new typedefs to serve as stand-ins
for the API types that have changed size between the two.

-- Scott



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to