Your approach is reasonable, as long as you can guarantee that the main app
calls Initialize() before any of the other modules have a chance to call
Terminate(). If your modules are only ever called from your main app,
consider forgoing the Initialize()/Terminate() calls in the modules
altogether - they're not buying you anything.
You can't call Initialize() after a final Terminate() because certain global
data initialized by Xerces are not reset by Terminate() to their starting
(pre-initialized) state. I've proposed a solution that I think would work,
but I haven't had time to implement it, and no one else has expressed much
interest in tilting at this particular windmill.
I don't know what happened to Covalent, but you can find the archives at
http://marc.theaimsgroup.com/?l=xerces-c-dev.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
