Paul, given your situation, I suggest that you make your API project into a DLL, but link it with the static Runtime Library. Then use method 2 to get the API project and the Crypto++ DLL to share the same heap. The rest of your application will then use a different heap.
> I really do not understand the need to reassign new and delete. There > are many dlls that allocate and free from the heap without doing this. The reason for this is that Crypto++ has an interface such that the DLL can free memory that's allocated by the application, and vice versa. > In any event, I am in the process of moving my application to .NET, at > which point we will not be using wxWidgets. Can the FIPS DLL be used with > .NET ? One method that should certainly work, although it may not be the most elegant, is to keep your API project as an unmanaged DLL that exports a C interface. I'm sure a .NET application should be able to call such a DLL. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [EMAIL PROTECTED] More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
