The idea of static cleanup objects dynamically added to a list as needed
makes sense, though I'm agnostic on the question of whether the objects
themselves should be static. (There aren't that many and they aren't that
big, so it can't make much difference either way.) There should be no
construction order issues, because all the static objects (including the
list object) should be initialized before we start running code that lazily
allocates memory. (FWIW, I now think you're right that construction order
wasn't an issue with the previous approach of building the list as static
objects are constructed. I suspect I was incorrectly thinking of
gXMLCleanupList as an object that needed to be constructed, rather than a
simple pointer. But you're right, it's cleaner not to add cleanups to the
list until you know you need them.)
Note, though, that there may be more than 8 instances where cleanups are
needed. I listed 21 candidates for cleanup in
http://marc.theaimsgroup.com/?l=xerces-c-dev&m=86952115511532&w=2. Some may
have been added or removed, and some may not actually need to be addressed.
As long as you've looked over my list and reviewed the code for all
platforms, I'm happy.
Thanks for taking this on. This is one of those issues that generates far
too much traffic on the list.
-jesse-
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
