Timeline for Why do library developers deliberately break existing code?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 5, 2021 at 22:03 | comment | added | Jonathan Wood | @MichaelKay: Which is the reason most of my obsolete members still remain in my stuff. No one said you have to remove it in the next version. Obviously, if I ever take it out, it could break code. But this provides an approach that can lessen the impact of breaking changes. | |
| Sep 5, 2021 at 21:35 | comment | added | Michael Kay | I find that many users upgrade in big jumps, they go straight from version N to version N+5. This means that the strategy of marking an interface as deprecated or obsolete in one release and then withdrawing it in the next is less effective than it might be. | |
| Sep 5, 2021 at 13:19 | history | answered | Jonathan Wood | CC BY-SA 4.0 |