On Monday, July 27, 2015 at 4:51:38 PM UTC-4, Jeffrey Walton wrote: > > C++11 is deprecating autor_ptr (or maybe its C++14). > > Below is the meat and potatoes of a patch to handle the deprecation so it > does not surprise us with a broken compile. The idea is if C++03, then we > want to use auto_ptr. If C++11, then we want to use unique_ptr. > > Crypto++'s use of auto_ptr did *not* involve sharing or ownership, so its > pretty much a straight switch from auto_ptr to unique_ptr when appropriate. > Also, auto_ptr vs unique_ptr is an internal implementation detail, so we > should not have a mess to clean up if applications and library use a > different compiler. >
I spent some more time researching this. Here are the four options for the update: https://programmers.stackexchange.com/questions/291141/how-to-handle-design-changes-for-auto-ptr-deprecation-in-c11. QUESTION: which method do you prefer? -- -- 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/d/optout.
