2010 IEEE International Conference on Software Maintenance 2010
DOI: 10.1109/icsm.2010.5609665
|View full text |Cite
|
Sign up to set email alerts
|

Index-based code clone detection: incremental, distributed, scalable

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
88
0
12

Year Published

2012
2012
2022
2022

Publication Types

Select...
6
1
1

Relationship

0
8

Authors

Journals

citations
Cited by 109 publications
(100 citation statements)
references
References 29 publications
0
88
0
12
Order By: Relevance
“…Hummel et al [14] were the first to use an index-based approach to scale clone detection to large inter-project repositories. Their technique detects only the Type-1 and Type-2 clones.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…Hummel et al [14] were the first to use an index-based approach to scale clone detection to large inter-project repositories. Their technique detects only the Type-1 and Type-2 clones.…”
Section: Related Workmentioning
confidence: 99%
“…General purpose clone detection is required for clone studies in large inter-project repositories and to help developers manage and merge their related software forks, as well as for use in the domain-specific activities. Scalable general purpose clone detection has been achieved by using deterministic [21] or non-deterministic [31] input partitioning and distributed execution of an existing non-scalable detector, using large distributed code indexes [14], or by comparing hashes after Type-1/2 normalization [15]. These existing techniques have a number of limitations.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…Hummel et al proposed indexbased code clone detection approach [19]. It detects Type-1 and Type-2 clones using MD5 hash function to calculate hash values from normalized statements.…”
Section: Related Workmentioning
confidence: 99%
“…It is not easy to maintain the clone of the code as compared to the original code [2]. Hence there is a need to remove the clones from the code, since cloning leaves adverse effects on the maintenance phase of the software [3].…”
Section: Introductionmentioning
confidence: 99%