Just being a trouble-maker:
As I understand it, the difference between the new and old DOM bindings is that the old one attempted to manage memory automagically, simulating the behavior under Java... whereas the new one requires explicit memory management (with, perhaps, some safety-net of having Nodes go away when their ownerDocument does). Is that an accurate enough summary? If so: I'd lean toward making the explicitly-managed version the basic Xerces C++ DOM API. But I wonder whether it would be possible/reasonable to also offer a derived/wrapper layer which provided automated memory management, for backward-compatability with old Xerces apps, and for the occasional case where a sloppy-but-easy-to-use solution is desirable. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
