The DOI matches its Crossref record.
"Cloning Considered Harmful" Considered Harmful
Abstract
Current literature on the topic of duplicated (cloned) code in software systems often considers duplication harmful to the system quality and the reasons commonly cited for duplicating code often have a negative connotation. While these positions are sometimes correct, during our case studies we have found that this is not universally true, and we have found several situations where code duplication seems to be a reasonable or even beneficial design option. For example, a method of introducing experimental changes to core subsystems is to duplicate the subsystem and introduce changes there in a kind of sandbox testbed. As features mature and become stable within the experimental subsystem, they can then be introduced gradually into the stable code base. In this way risk of introducing instabilities in the stable version is minimized. This paper describes several patterns of cloning that we have encountered in our case studies and discusses the advantages and disadvantages associated with using them
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cited by
Roy, C. K., & Cordy, J. R. (2008) · 2008 16th IEEE International Conference on Program Comprehension · doi:10.1109/icpc.2008.41 · Cited by 533
“Cloning considered harmful” considered harmful: patterns of cloning in software
Kapser, C. J., & Godfrey, M. W. (2008) · Empirical Software Engineering · doi:10.1007/s10664-008-9076-6 · Cited by 365
Self-citationThe road ahead for Mining Software Repositories
Hassan, A. E. (2008) · 2008 Frontiers of Software Maintenance · doi:10.1109/fosm.2008.4659248 · Cited by 337
Juergens, E., Deissenboeck, F., Hummel, B., & Wagner, S. (2009) · 2009 IEEE 31st International Conference on Software Engineering · doi:10.1109/icse.2009.5070547 · Cited by 318
An Empirical Study of Function Clones in Open Source Software
Roy, C. K., & Cordy, J. R. (2008) · 2008 15th Working Conference on Reverse Engineering · doi:10.1109/wcre.2008.54 · Cited by 137
“They provide a detailed categorization of code clones in the form of a taxonomy [15], propose a new analysis framework [14] and give an in-depth study on the harmfulness / usefulness of cloning [13].”
Background
Metadata
- Authors
- Kapser, C., & Godfrey, M.
- Venue
- 2006 13th Working Conference on Reverse Engineering
- Publisher
- IEEE
- Published
- 2006
- Pages
- 19-28
- ISSN
- 1095-1350 (ISSN-L)
- OpenAlex
- W2101251407
- Cited by
- 251
- References
- 0
- FWCI
- 17.70
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: "Cloning Considered Harmful" Considered Harmful. https://app.cochat.ai/papers/10.1109/wcre.2006.1
- The paper
- Kapser, C., & Godfrey, M. (2006). "Cloning Considered Harmful" Considered Harmful. 2006 13th Working Conference on Reverse Engineering. https://doi.org/10.1109/wcre.2006.1
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.