2018 IEEE 12th International Workshop on Software Clones (IWSC) 2018
DOI: 10.1109/iwsc.2018.8327312
|View full text |Cite
|
Sign up to set email alerts
|

Are there functionally similar code clones in practice?

Abstract: Having similar code fragments, also called clones, in software systems can lead to unnecessary comprehension, review and change efforts. Syntactically similar clones can often be encountered in practice. The same is not clear for only functionally similar clones (FSC).We conducted an exploratory survey among developers to investigate whether they encounter functionally similar clones in practice and whether there is a difference in their inclination to remove them to syntactically similar clones.Of the 34 deve… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
7
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
7
1
1

Relationship

0
9

Authors

Journals

citations
Cited by 14 publications
(7 citation statements)
references
References 13 publications
0
7
0
Order By: Relevance
“…To find candidates, we explored code clone benchmarks [18], [19], [20], [21], [22], code search engines, open-source platforms like GitHub, and practice websites like Codewars 1 and LeetCode. 2 We manually modified some snippets to control our variables but wrote none from scratch.…”
Section: B Artifact Collectionmentioning
confidence: 99%
See 1 more Smart Citation
“…To find candidates, we explored code clone benchmarks [18], [19], [20], [21], [22], code search engines, open-source platforms like GitHub, and practice websites like Codewars 1 and LeetCode. 2 We manually modified some snippets to control our variables but wrote none from scratch.…”
Section: B Artifact Collectionmentioning
confidence: 99%
“…These resources altogether contain a massive quantity of diverse applications, but despite this diversity, a significant amount of code contains similar features [1]. This repetition occurs for a variety of reasons: for example, similar sub-problems reoccur in different contexts [2], development communities share linguistic conventions [3], and developers directly reuse and modify each other's code [4]. This repetition from a diversity of sources means not only that a given algorithm may exist somewhere already and be waiting for discovery, but also that there may exist multiple similar but divergent alternatives that satisfy the problem.…”
Section: Introductionmentioning
confidence: 99%
“…Code similarity has been extensively studied in literature [12], particularly type-4 (semantically similar) code clones. Through a user study, researchers showed that functionally similar code exists in practice [13]. While static token based approaches such as SourcererCC [14] and CCFinder [15] have been studied, advances in computing has paved the path for two other approaches to code clone detection.…”
Section: Related Workmentioning
confidence: 99%
“…Most current studies exclude Type 4 clones because of the lack of tool support [16], [12], [13], [17], [18]. Nevertheless, Type 4 clones exist, and recent research efforts try to deepen the understanding of them [15], [19], [20]. This work provides a significant contribution to semantic clone detection in the form of novel concepts and a prototype implementing them.…”
Section: Introductionmentioning
confidence: 99%