"Cloning Considered Harmful" Considered Harmful
By Cory J. Kapser, Michael W. Godfrey. Working Conference on Reverse Engineering, 2006
296 citations recorded by the source corpus.
View Paper: https://www.semanticscholar.org/paper/3f0696516d83f9a40a23509068224835377b3d17
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
- Ahmed E. Hassan
- Joost Visser
- Ying Zou
- F. Deißenböck
- Iman Keivanloo
- B. Hummel
- Elmar Jürgens
- Ilja Heitlager
Citations in the corpus
- The road ahead for Mining Software Repositories (2008, background): “Kapser and Godfrey examine several large open source systems and show that cloning is often used as a principled engineering tool [34].”
- Do code clones matter? (2009, background): “In fact, some researchers even started to doubt the harmfulness of cloning at all [17].”
- An Empirical Study of Function Clones in Open Source Software (2008, background): “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].”
- A Practical Model for Measuring Maintainability (2007, background): “Though the occurrence of a small amount of duplication is natural, excessive amounts of duplication are detrimental to its main-tainability, in particular to the characteristics of analysability and changeability [18].”
- Learning to rank code examples for code search engines (2017, background): “Code reuse also contributes to the quality of products in software development [30].”
- NICAD: Accurate Detection of Near-Miss Intentional Clones Using Flexible Pretty-Printing and Code Normalization (2008, background): “it is beneficial in certain situations [21], one of the major difficulties with such duplicated fragments is that if a bug is detected in a code fragment, all the fragments similar to it should be investigated to check for same bug [25].”