On Monday, November 4, 2013 12:10:18 PM UTC-5, Arendell wrote: > > MD5 hash; >> byte buffer[2 * MD5::DIGESTSIZE]; >> >> FileSource f(argv[1], true, >> new HashFilter(hash, >> new HexEncoder(new ArraySink(buffer,2 * MD5::DIGESTSIZE)))); >> >> > Is this way cause a memory leak? > No.
>From Readme.txt: *** Important Usage Notes *** 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. 2. Crypto++ is thread safe at the class level. This means you can use Crypto++ safely in a multithreaded application, but you must provide synchronization when multiple threads access a common Crypto++ object. -- -- 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. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
