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 developers answering the survey, 31 have experienced FSC in their professional work, and 24 have experienced problems caused by FSCs. We found no difference in the inclination and reasoning for removing FSCs and syntactically similar clones. FSCs exist in practice and should be investigated to bring clone detectors to the same quality as for syntactically similar clones, because being able to detect them allows developers to manage and potentially remove them.
%0 Conference Paper
%1 kafer2018there
%A Käfer, Verena
%A Wagner, Stefan
%A Koschke, Rainer
%B 2018 IEEE 12th International Workshop on Software Clones (IWSC)
%D 2018
%I IEEE
%K iste-se myown
%R 10.1109/IWSC.2018.8327312
%T Are there functionally similar code clones in practice?
%X 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 developers answering the survey, 31 have experienced FSC in their professional work, and 24 have experienced problems caused by FSCs. We found no difference in the inclination and reasoning for removing FSCs and syntactically similar clones. FSCs exist in practice and should be investigated to bring clone detectors to the same quality as for syntactically similar clones, because being able to detect them allows developers to manage and potentially remove them.
@inproceedings{kafer2018there,
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 developers answering the survey, 31 have experienced FSC in their professional work, and 24 have experienced problems caused by FSCs. We found no difference in the inclination and reasoning for removing FSCs and syntactically similar clones. FSCs exist in practice and should be investigated to bring clone detectors to the same quality as for syntactically similar clones, because being able to detect them allows developers to manage and potentially remove them.},
added-at = {2018-08-16T16:39:18.000+0200},
author = {Käfer, Verena and Wagner, Stefan and Koschke, Rainer},
biburl = {https://puma.ub.uni-stuttgart.de/bibtex/2907f1679b5ba798c09996653c2ef6fcb/verenakaefer},
booktitle = {2018 IEEE 12th International Workshop on Software Clones (IWSC)},
doi = {10.1109/IWSC.2018.8327312},
interhash = {b798f6689eb95ef73f9b1a795058c0e4},
intrahash = {907f1679b5ba798c09996653c2ef6fcb},
keywords = {iste-se myown},
publisher = {IEEE},
timestamp = {2018-08-16T14:39:18.000+0200},
title = {Are there functionally similar code clones in practice?},
year = 2018
}
