----- Original Message ----- From: "Wei Dai" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, March 22, 2003 5:34 PM Subject: Re: I'm confused.
| I've been avoiding advanced use of auto_ptr (such as in function | interfaces) because the standard on it was finalized at a late date and as | a result many compilers has non-standard implementations. I think VC6 | still has a non-standard implementaiton of auto_ptr. When Crypto++ stops | supporting VC6, maybe I'll switch at that point. | | On Fri, Mar 21, 2003 at 10:11:18PM -0800, Michael Hunley wrote: | > Actually, I think many people get tripped up by that (and other similar | > constructs); I know I did the first time. Wei, wouldn't it be more clear | > to have those functions/constructors that take pointers to objects that | > they expect to come from the heap, which they will later free for you, take | > them as auto_ptr's? Then it would be clear that you are giving up control | > of that memory (and responsibility) and that it had to come from the heap | > by default. Furthermore, it would also let client code use it's own | > allocator's if it really wanted to without adding any hassle to the core | > Crypto++ code. Am I missing something? | > | > michael Hi Wei, | When Crypto++ stops | supporting VC6, maybe I'll switch at that point. There does exist an audience for the VC++ support. The support is appreciated. Jeff
