> There's a new wiki page on config.h. It can be found at > http://cryptopp.com/wiki/config.h. > > It provides explanations for the seemingly endless array of defines. It > also attempts to document some of their interactions. > > It also provides recommendations for defines that you should consider > using eventhough they are not enabled by default. >
A couple of defines were added for 5.6.3 related to compatibility. They are documented at https://cryptopp.com/wiki/Config.h#Compatibility_Defines. The short of it is there's a new define, MAINTAIN_BACKWARDS_COMPATIBILITY_562, that's off by default. That allows people who upgrade to get all the benefits, like removal of the remaining [known] undefined behavior. Those who need 5.6.2 patch-level compatibility can define MAINTAIN_BACKWARDS_COMPATIBILITY_562. If they define it, then they get the undefined behavior that we could not remove without breaking compatibility. MAINTAIN_BACKWARDS_COMPATIBILITY_562 will probably go away at Crypto++ 6.0. Its not going to linger on for decades like MAINTAIN_BACKWARDS_COMPATIBILITY. It was meant to help people upgrade or give people a choice. Jeff -- -- 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.
