Cloning and copying between GNOME projects

Krinke, Jens; Gold, Nicolas; Jia, Yunyi; Binkley, David

doi:10.1109/msr.2010.5463290

Cited by 35 publications

(15 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…ArgoUML has been used in many previous studies on the evolution of code clones [1,[12][13][14][15]. Besides, other empirical studies have looked at ArgoUML and it can be considered a well-studied system.…”

Section: Study Setupmentioning

confidence: 99%

“…The last change date information from version control systems has been used by Krinke et al [15,16] to compare the history of clone pairs and distinguish the original from the copied code. Their approach is able to do the distinction for the majority of clone pairs even between different projects (they analyzed the subprojects of the GNOME Desktop Suite).…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Is cloned code older than non-cloned code?

Krinke

2011

Proceedings of the 5th International Workshop on Software Clones

Self Cite

View full text Add to dashboard Cite

It is still a debated question whether cloned code causes increased maintenance efforts. If cloned code is more stable than non-cloned code, i.e. it is changed less often, it will require less maintenance efforts. The more stable cloned code is, the longer it will not have been changed, so the stability can be estimated through the code's age. This paper presents a study on the average age of cloned code.For three large open source systems, the age of every line of source code is computed as the date of the last change in that line. In addition, every line is categorized whether it belongs to cloned code as detected by a clone detector. The study shows that on average, cloned code is older than non-cloned code. Moreover, if a file has cloned code, the average age of the cloned code of the file is lower than the average age of the non-cloned code in the same file. The results support the previous findings that cloned code is more stable than non-cloned code.

show abstract

Section: Study Setupmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Is cloned code older than non-cloned code?

Krinke

2011

Proceedings of the 5th International Workshop on Software Clones

Self Cite

View full text Add to dashboard Cite

show abstract

“…Several studies [18,32,22] have provided evidence for widespread presence of clones and there has been much interest and previous work on software engineering applications and implications such as software evolution [21,36,7,3,29], refactoring [4], and bug detection [24,31,23]. Many tools and techniques for detecting clones have been studied [34].…”

Section: Introductionmentioning

confidence: 99%

“…To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. ESEC/FSE '13, August [18][19][20][21][22][23][24][25][26]2013, Saint Petersburg, Russia Copyright 13 ACM 978-1-4503-2237-9/13/08 ...$15.00.…”

Section: Introductionmentioning

confidence: 99%

Searching for better configurations: a rigorous approach to clone evaluation

Wang

Harman

Jia

et al. 2013

Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering

Self Cite

131

105

View full text Add to dashboard Cite

Clone detection finds application in many software engineering activities such as comprehension and refactoring. However, the confounding configuration choice problem poses a widely-acknowledged threat to the validity of previous empirical analyses. We introduce desktop and parallelised cloud-deployed versions of a search based solution that finds suitable configurations for empirical studies. We evaluate our approach on 6 widely used clone detection tools applied to the Bellon suite of 8 subject systems. Our evaluation reports the results of 9.3 million total executions of a clone tool; the largest study yet reported. Our approach finds significantly better configurations (p < 0.05) than those currently used, providing evidence that our approach can ameliorate the confounding configuration choice problem.

show abstract

“…The presented approach was also used to study how code is copied and cloned between subprojects of the GNOME Desktop Suite [23]. The case study revealed a complex flow of reused code between the different subprojects.…”

Section: Related Workmentioning

confidence: 99%

Distinguishing copies from originals in software clones

Krinke

Gold

Jia

et al. 2010

Proceedings of the 4th International Workshop on Software Clones

Self Cite

View full text Add to dashboard Cite

Cloning is widespread in today's systems where automated assistance is required to locate cloned code. Although the evolution of clones has been studied for many years, no attempt has been made so far to automatically distinguish the original source code leading to cloned copies. This paper presents an approach to classify the clones of a clone pair based on the version information available in version control systems. This automatic classification attempts to distinguish the original from the copy. It allows for the fact that the clones may be modified and thus consist of lines coming from different versions. An evaluation, based on two case studies, shows that when comments are ignored and a small tolerance is accepted, for the majority of clone pairs the proposed approach can automatically distinguish between the original and the copy.

show abstract

Cloning and copying between GNOME projects

Cited by 35 publications

References 19 publications

Is cloned code older than non-cloned code?

Is cloned code older than non-cloned code?

Searching for better configurations: a rigorous approach to clone evaluation

Distinguishing copies from originals in software clones

Contact Info

Product

Resources

About