Hi David, David Bertoni <[EMAIL PROTECTED]> writes:
> I doubt there are many MemoryManager implementations out there period, much > less users who are going to be hit by this bug. And they can find it just > by testing properly. We are debating two options: 1. We should keep the API unchanged in order not to inconvenience a small number of users. 2. We should change the API in order to help a small number of users fix a bug. For me when choosing between a mere inconvenience and a bug fix, the answer is quite obvious. I am also pretty sure you would make this function pure virtual if you were designing the interface from scratch. So let's just do the right thing here. I've added additional information to the getExceptionMemoryManager documentation. Boris -- Boris Kolpackov, Code Synthesis Tools Open source XML data binding for C++: http://codesynthesis.com/products/xsd Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
