2.9, 3.0: Backward-incompatible changes
pfalcon opened this issue · 2 comments
pfalcon commented
Soft backward-incompatibility:
- Public API structures and their fields are renamed to follow
standard_c_naming_convention
. However, compatibility defines are provided to lessen immediate impact on 3rd-party applications. The defines are guaranteed to be available at least for half a year, but may be removed in uzlib releases beyond that. The applications are recommended to update soon. The list of renames can be seen here: https://github.com/pfalcon/uzlib/blob/master/src/tinf_compat.h
Required changes:
pfalcon commented
Ok, my idea was to batch any backward-incompatible API changes before 3.0, but that takes longer than expected, so let there be 2.9.x series with API in flux. Hope to cut a release soon.
pfalcon commented
Closing now.