Identifying Changed Source Code Lines from Version Repositories
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Assessing the impact of bad smells using historical information
Ninth international workshop on Principles of software evolution: in conjunction with the 6th ESEC/FSE joint meeting
"Cloning considered harmful" considered harmful: patterns of cloning in software
Empirical Software Engineering
Comparison and evaluation of code clone detection techniques and tools: A qualitative approach
Science of Computer Programming
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
An empirical study on the maintenance of source code clones
Empirical Software Engineering
Clone region descriptors: Representing and tracking duplication in source code
ACM Transactions on Software Engineering and Methodology (TOSEM)
Near-miss function clones in open source software: an empirical study
Journal of Software Maintenance and Evolution: Research and Practice - Working Conference on Reverse Engineering (WCRE 2008)
Achieving accurate clone detection results
Proceedings of the 4th International Workshop on Software Clones
Are scripting languages really different?
Proceedings of the 4th International Workshop on Software Clones
Clone removal: fact or fiction?
Proceedings of the 4th International Workshop on Software Clones
Distinguishing copies from originals in software clones
Proceedings of the 4th International Workshop on Software Clones
Proceedings of the 4th International Workshop on Software Clones
Are clones harmful for maintenance?
Proceedings of the 4th International Workshop on Software Clones
Oops! . . . I changed it again
Proceedings of the 5th International Workshop on Software Clones
Is cloned code older than non-cloned code?
Proceedings of the 5th International Workshop on Software Clones
Frequency and risks of changes to clones
Proceedings of the 33rd International Conference on Software Engineering
An empirical study of long-lived code clones
FASE'11/ETAPS'11 Proceedings of the 14th international conference on Fundamental approaches to software engineering: part of the joint European conferences on theory and practice of software
Capturing and analyzing low-level events from the code editor
Proceedings of the 3rd ACM SIGPLAN workshop on Evaluation and usability of programming languages and tools
A method for analyzing code homology in genealogy of evolving software
FASE'10 Proceedings of the 13th international conference on Fundamental Approaches to Software Engineering
An empirical study on inconsistent changes to code clones at the release level
Science of Computer Programming
Harmfulness of code duplication: a structured review of the evidence
EASE'09 Proceedings of the 13th international conference on Evaluation and Assessment in Software Engineering
Comparative stability of cloned and non-cloned code: an empirical study
Proceedings of the 27th Annual ACM Symposium on Applied Computing
An empirical study on clone stability
ACM SIGAPP Applied Computing Review
Understanding the evolution of type-3 clones: an exploratory study
Proceedings of the 10th Working Conference on Mining Software Repositories
An empirical study of the fault-proneness of clone mutation and clone migration
Proceedings of the 10th Working Conference on Mining Software Repositories
Enhancement of CRD-based clone tracking
Proceedings of the 2013 International Workshop on Principles of Software Evolution
An empirical study of the factors affecting co-change frequency of cloned code
CASCON '13 Proceedings of the 2013 Conference of the Center for Advanced Studies on Collaborative Research
| Hi-index | 0.00 |
Despite the conventional wisdom concerning the risks related to the use of source code cloning as a software development strategy, several studies appeared in literature indicated that this is not true. In most cases clones are properly maintained and, when this does not happen, is because cloned code evolves independently. Stemming from previous works, this paper combines clone detection and co-change analysis to investigate how clones are maintained when an evolution activity or a bug fixing impact a source code fragment belonging to a clone class. The two case studies reported confirm that, either for bug fixing or for evolution purposes, most of the cloned code is consistently maintained during the same co-change or during temporally close co-changes.