Construct · 1 fields · 1 citations

API breaking changes: a standalone construct

One name. One construct. A landmark on the map.

● anchor · a standalone construct Nearest construct by meaning·not indexed

A single standalone construct; nearby constructs are located against it in the Collider. Tap a field for its definition, unit, and measures.

Software engineering

changes to a library interface that break dependent code, studied for how ecosystems negotiate who bears the cost.

In software engineering, API breaking changes refers to changes to a library interface that break dependent code, studied for how ecosystems negotiate who bears the cost. This meaning comes from Bogart (2016) in Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering.[1]

Unit
Recovery means
Measured by

Run it through the Collider, or take the citations with you.

See how API breaking changes sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in Collider Export BibTeX Report this entry

Nearby constructs

break2 fields · 4 citationsjingle · one word, two constructs code3 fields · 6 citationsjingle · one word, three constructs compatibility6 fields · 10 citationsjingle · one name, six constructs

References

Bogart, C., Kästner, C., Herbsleb, J., & Thung, F. (2016). How to break an API: cost negotiation and community values in three software ecosystems. Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering. https://doi.org/10.1145/2950290.2950325

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct