Most of the suggestions in this book tell you to keep things compatible, always to design libraries and APIs compatibly, and never to do anything that could break the code of any of your API’s clients. This means that you shouldn’t remove a method, field, class, or package from an API, because doing so is likely to create an incompatibility for some potential client. As a result, you can either leave a library unmodified or you can add new items to it. An interesting question to ask is what would happen if developers started behaving like this. Wouldn’t the amount of code grow without any limitation whatsoever? Wouldn’t developers spend most of their time maintaining existing libraries? Would developers have the time to write any new code at all?
Swipe to navigate through the chapters of this book
Please log in to get access to this content
To get access to this content you need the following product:
- End-of-Life Procedures
- Sequence number
- Chapter number
- Chapter 19