On Tue, Apr 14, 2015 at 1:27 PM, Alan Conway <[email protected]> wrote:
> That works for me, now how do we manage the transition? I don't think we > can afford to inflict "yum update proton; all proton apps crash" on our > users. That means we cannot change the behavior of existing function > names. I don't much like adding encode_foo2 for every encode_foo but I > don't see what else to do. > We could mark the old ones as deprecated and add the new ones as pn_xxx_encode2 and provide a feature macro that #defines pn_xxx_encode to pn_xxx_encode2. Then after a sufficient transition period we can get rid of the old versions. --Rafael
