> > Take the encryption code for example. You allocate memory > > for 'encryptor' but I never see you delete them in your code.
> In the example I gave I did not bother deleting the encryptor object, > letting the memory be reclaimed after the program completes. Yeah. I just wondered without using the 'delete' operator how the object is destroyed and memory is freed. And this seems to be the answer >From the readme file: "1. If a constructor for A takes a pointer to an object B (except primitive types such as int and char), then A owns B and will delete B at A's destruction. If a constructor for A takes a reference to an object B, then the caller retains ownership of B and should not destroy it until A no longer needs it." --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
