Boris Kolpackov wrote:
Hi David,
David Bertoni <[EMAIL PROTECTED]> writes:
Are there any objections if I make some API changes that will result in
explicit use of the MemoryManager class when creating a transcoding
service and creating transcoders?
Is it not possible to make the choice default to the global memory manager
and thus retain backwards-compatibility? I am not exactly clear what you
plan to change. Perhaps you could outline the changes you are proposing
(e.g., which extra argument are added to which functions).
We could maintain backward compatibility, but these functions are only
used internally, so there shouldn't be any issues. Also, the very
presence of default MemoryManager arguments is what introduced the bug
in the first place:
// ----------------------------------------------------------------
// Constructors and Destructor
// ----------------------------------------------------------------
XMLMutex(MemoryManager* const manager = XMLPlatformUtils::fgMemoryManager);
I will post a proposal with the changes as soon as I can.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
