Publication: To react, or not to react: Patterns of reaction to API deprecation
To react, or not to react: Patterns of reaction to API deprecation
Date
Date
Date
Citations
Sawant, A. A., Robbes, R., & Bacchelli, A. (2020). To react, or not to react: Patterns of reaction to API deprecation. Empirical Software Engineering, 24(6), 3824–3870. https://doi.org/10.1007/s10664-019-09713-w
Abstract
Abstract
Abstract
Application Programming Interfaces (API) provide reusable functionality to aid developers in the development process. The features provided by these APIs might change over time as the API evolves. To allow API consumers to peacefully transition from older obsolete features to new features, API producers make use of the deprecation mechanism that allows them to indicate to the consumer that a feature should no longer be used. The Java language designers noticed that no one was taking these deprecation warnings seriously and continued u
Additional indexing
Creators (Authors)
- Sawant, Anand Ashok
- Robbes, Romain
- Bacchelli, Alberto
Volume
Volume
Volume
Number
Number
Number
Page range/Item number
Page range/Item number
Page range/Item number
Page end
Page end
Page end
Item Type
Item Type
Item Type
In collections
Dewey Decimal Classifikation
Dewey Decimal Classifikation
Dewey Decimal Classifikation
Scope
Scope
Scope
Language
Language
Language
Publication date
Publication date
Publication date
Date available
Date available
Date available
ISSN or e-ISSN
ISSN or e-ISSN
ISSN or e-ISSN
OA Status
OA Status
OA Status
Free Access at
Free Access at
Free Access at
Publisher DOI
Other Identification Number
Other Identification Number
Other Identification Number
Citations
Sawant, A. A., Robbes, R., & Bacchelli, A. (2020). To react, or not to react: Patterns of reaction to API deprecation. Empirical Software Engineering, 24(6), 3824–3870. https://doi.org/10.1007/s10664-019-09713-w
