Are there any plans to migrate the BDB project to Visual Studio 2005?

Question

The problem is when BDB is linked into an application built with VS8, deleting some BDB objects results in mixing memory managers and application crashes.
That is, if BDB is built with VS6, the BDB DLL will use VS6's new and delete operators. If the application that uses BDB is built with VS8 its objects will be allocated using VS8's new and delete:
DbSequence *seq = new DbSequence(db, 0);
delete seq;
The first line calls application's new and then the DbSequence constructor. The second line, on the other hand, calls the destructor, which in turn calls the operator delete (Microsoft's "scalar deleting destructor"). The destructor resides in the BDB DLL, so the delete call is made in the context of the DLL, trying to delete the memory block that was allocated by the executable.

Answer 1

Thank you for the reply, Michael.
I finally have been able to work around all inter-DLL dependencies between VS6 and VS8 builds. You may want to mention in README the fact that if C++ interface is used, the application is expected to be built with the same compiler used to build BDB, even if custom callbacks for malloc, realloc and free are used in the code.
The BDB project builds partially in VS2005. A few subprojects fail by default and the db_dll project requires a couple of small fixes. For example, advapi32.lib is missing from the list of input libraries in db_dll project (SetSecurityDescriptorDacl and InitializeSecurityDescriptor). The resulting DLL seems to work fine.
Also, those applications that build with 32-bit time_t will fail to link. It's easy to fix, but I wonder if this will have any effect on the format of the database.
Andre