On Fri, Mar 16, 2012 at 09:22, Rod <[email protected]> wrote: > Great, thanks! It's generally concerning when you see a "new" without > a corresponding "delete", it might be helpful to have this behavior > (implicit destruction of objects passed into the constructor) documented in > the wiki. Thanks for your help. > > Now I remember where I saw it documented. From 'Readme.txt' included with crypto++:
""" 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. """ Geoff -- 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.
