Must have missed that, thanks very much, Michael. - Shawn
> -----Original Message----- > From: Michael Mertens [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 19, 2002 1:05 PM > To: [EMAIL PROTECTED] > Subject: Re: cryptest and new (but no delete) > > > > I noticed that in crypttest, in functions like > DefaultEncryptorForMAC, there > > are references to "new", but without appropriate > "delete"'s...such as with > > the call to new HexEncoder and new StringSink. > > > > Is cryptest leaking memory? Or is there something special about > "new" going > > on here that I'm not aware of? > > cite from readme.txt: > > 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. > > Greetings, > Michael > >
