Beyond templates: a study of clones in the STL and some general implications

Basit, Hamid Abdul; Rajapakse, D.C.; Jarzabek, Stan

doi:10.1109/icse.2005.1553588

Cited by 21 publications

(27 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although most consider code clones to be identical or near identical fragments of source code [9,19], code clones have no consistent or precise definition in the literature. Indeed, a "clone" has been defined operationally based on the computation of individual clone detectors.…”

Section: Related Workmentioning

confidence: 99%

An empirical study of code clone genealogies

KimMiryung

SazawalVibha

NotkinDavid

et al. 2005

SIGSOFT Softw. Eng. Notes

199

204

View full text Add to dashboard Cite

It has been broadly assumed that code clones are inherently bad and that eliminating clones by refactoring would solve the problems of code clones. To investigate the validity of this assumption, we developed a formal definition of clone evolution and built a clone genealogy tool that automatically extracts the history of code clones from a source code repository. Using our tool we extracted clone genealogy information for two Java open source projects and analyzed their evolution.Our study contradicts some conventional wisdom about clones. In particular, refactoring may not always improve software with respect to clones for two reasons. First, many code clones exist in the system for only a short time; extensive refactoring of such short-lived clones may not be worthwhile if they are likely diverge from one another very soon. Second, many clones, especially long-lived clones that have changed consistently with other elements in the same group, are not easily refactorable due to programming language limitations. These insights show that refactoring will not help in dealing with some types of clones and open up opportunities for complementary clone maintenance tools that target these other classes of clones.

show abstract

Section: Related Workmentioning

confidence: 99%

An empirical study of code clone genealogies

KimMiryung

SazawalVibha

NotkinDavid

et al. 2005

SIGSOFT Softw. Eng. Notes

199

204

View full text Add to dashboard Cite

show abstract

“…Jarzabek et al [20] and Basit et al [6] performed case studies for reducing duplication in on the Java buffer classes and the STL. In their studies, they used a meta-language XVCL to reconstruct the code at compile time.…”

Section: Related Workmentioning

confidence: 99%

“…In [20] many clones existed because of language limitations and were removed using templates. In [6] the STL made heavy use of generics to reduce redundant code but redundant code still existed in a form analogous to customization and boiler-plating patterns where operators were modified.…”

Section: Related Workmentioning

confidence: 99%

"Cloning Considered Harmful" Considered Harmful

Kapser

Godfrey

2006

2006 13th Working Conference on Reverse Engineering

180

125

View full text Add to dashboard Cite

show abstract

“…Limitations of (object-oriented) programming languages are discussed as a reason for code clones [8,43]. Mechanisms such as inheritance or generics are not always sufficient for reusing functionality or expressing variability in programs and thus contribute to code cloning.…”

Section: Reasoning About Code Clones Inmentioning

confidence: 99%

Code clones in feature-oriented software product lines

Schulze

Apel

Kästner

2010

Proceedings of the Ninth International Conference on Generative Programming and Component Engineering

View full text Add to dashboard Cite

Some limitations of object-oriented mechanisms are known to cause code clones (e.g., extension using inheritance). Novel programming paradigms such as feature-oriented programming (FOP) aim at alleviating these limitations. However, it is an open issue whether FOP is really able to avoid code clones or whether it even facilitates (FOP-related) clones. To address this issue, we conduct an empirical analysis on ten feature-oriented software product lines with respect to code cloning. We found that there is a considerable amount of clones in feature-oriented software product lines and that a large fraction of these clones is FOP-related (i.e., caused by limitations of feature-oriented mechanisms). Based on our results, we initiate a discussion on the reasons for FOP-related clones and on how to cope with them. We exemplary show how such clones can be removed by the application of refactoring.

show abstract

Beyond templates: a study of clones in the STL and some general implications

Cited by 21 publications

References 0 publications

An empirical study of code clone genealogies

An empirical study of code clone genealogies

"Cloning Considered Harmful" Considered Harmful

Code clones in feature-oriented software product lines

Contact Info

Product

Resources

About