Code reuse: Difference between revisions

Revision as of 01:58, 18 January 2023

Revision as of 01:11, 28 February 2023

Line 5:

Code reuse may be achieved by different ways depending on a complexity of a [[programming language]] chosen and range from a lower-level approaches like code [[Cut, copy, and paste|copy-pasting]] (e.g. via [[Snippet (programming)|snippets]]),<ref>{{Cite journal|last1=Selaolo|first1=Karabo|last2=Hlomani|first2=Hlomani|date=2016|title=Towards An Algorithms Ontology Cluster: for Modular Code Reuse and Polyglot Programming|url=https://www.researchgate.net/publication/305144699|journal=Advances in Computer Science|volume=5|pages=63|via=Researchgate}}</ref> simple functions ([[Procedure (computer science)|procedure]]s or [[subroutine]]s) or a bunch of [[Object (computer science)|objects]] or [[Subroutine|functions]] organized into [[Modular programming|module]]s (e.g. [[Library (computing)|libraries]])<ref>{{Cite web|title=4. Code Reuse: Functions and Modules - Head First Python, 2nd Edition [Book]|url=https://www.oreilly.com/library/view/head-first-python/9781491919521/ch04.html|access-date=2022-01-26|website=www.oreilly.com|language=en}}</ref>{{r|Reddy2011|page=7|}} or custom [[namespace]]s, and [[Package manager|package]]s, [[Framework (computer science)|framework]]s or [[software suite]]s in higher-levels.

Code reuse implies dependencies which can make [[Software maintenance|code maintanabilitymaintainability]] harder.{{Citation needed}} At least one study found that code reuse reduces [[technical debt]].<ref>{{Cite journal|last1=Feitosa|first1=Daniel|last2=Ampatzoglou|first2=Apostolos|last3=Gkortzis|first3=Antonios|last4=Bibi|first4=Stamatia|last5=Chatzigeorgiou|first5=Alexander|date=September 2020|title=CODE reuse in practice: Benefiting or harming technical debt|url=https://linkinghub.elsevier.com/retrieve/pii/S0164121220300960|journal=Journal of Systems and Software|language=en|volume=167|pages=110618|doi=10.1016/j.jss.2020.110618|s2cid=219502749}}</ref>

==Overview==