Abstract
The previous chapter tried to prove that maintaining a library with an API is not more costly than maintaining code without an API. However, that doesn’t mean that you’ll simplify your life by adding an API to your code—not at all. All that has been proved is that if you are able to write code of a certain level of quality, you won’t complicate your maintainer’s life by adding an API to it, especially if you follow the evolution guidelines outlined in this book.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Bibliography
Ulrich Drepper, “How to Write Shared Libraries (2006), http: //people. redhat. com/drepper/dsohowto.pdf.
Rights and permissions
Copyright information
© 2008 Jaroslav Tulach
About this chapter
Cite this chapter
(2008). Evolving the API Universe. In: Practical API Design. Apress. https://doi.org/10.1007/978-1-4302-0974-4_15
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0974-4_15
Publisher Name: Apress
Print ISBN: 978-1-4302-0973-7
Online ISBN: 978-1-4302-0974-4
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)