On the use of replacement messages in API deprecation: An empirical study.
Saved in:
| Title: | On the use of replacement messages in API deprecation: An empirical study. |
|---|---|
| Authors: | Brito, Gleison1 gleison@dcc.ufmg.br, Hora, Andre2 hora@facom.ufms.br, Valente, Marco Tulio1 mtov@dcc.ufmg.br, Robbes, Romain3 rrobbes@unibz.it |
| Source: | Journal of Systems & Software. Mar2018, Vol. 137, p306-321. 16p. |
| Subjects: | Application program interfaces, Code reuse, Software libraries (Computer programming), Java programming language, Computer software development |
| Abstract: | Libraries are commonly used to support code reuse and increase productivity. As any other system, they evolve over time, and so do their APIs. Consequently, client applications should be updated to benefit from better APIs. To facilitate this task, API elements should always be deprecated with replacement messages. However, in practice, there are evidences that API elements are deprecated without these messages. In this paper, we study questions regarding the adoption of deprecation messages. Our goal is twofold: to measure the real usage of deprecation messages and to investigate whether a tool is needed to recommend them. We assess (i) the frequency of deprecated elements with replacement messages, (ii) the impact of software evolution on this frequency, and (iii) the characteristics of systems that deprecate API elements in a correct way. Our analysis on 622 Java and 229 C# systems shows that: (i) on the median, 66.7% and 77.8% of the API elements are deprecated with replacement messages per project, (ii) there is no major effort to improve deprecation messages, and (iii) systems that deprecated API elements with messages are different in terms of size and community. As a result, we provide the basis for creating a tool to support clients detecting missing deprecation messages. [ABSTRACT FROM AUTHOR] |
| Copyright of Journal of Systems & Software is the property of Elsevier B.V. and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.) | |
| Database: | Engineering Source |
Be the first to leave a comment!
