Cloned code: stable code
Cloned code: stable code
复制标题
DOI：
10.1002/smr.1551
复制
发表时间：
2013-10
期刊：
影响因子：
--
通讯作者：
Jan Harder;Nils Göde
中科院分区：
文献类型：
--
作者：
Jan Harder;Nils Göde
据说，代码克隆威胁到系统的维护，尤其是在更改源代码时，是否可以通过比较克隆代码的稳定性与非固定代码的稳定性来分析发现克隆的代码比非限制的代码更稳定，因此，可能需要更少的维护工作 - 对本文经常声音的假设。使用更细化的测量，我们将研究进一步扩展到学术界和行业的主题系统，并评估不同的克隆检测参数对克隆稳定性的影响，以及我们一般而言的稳定性。尽管如此，我们的结果也表明，克隆的稳定性根据克隆的特征，相应的项目环境和随着时间的推移而有所不同©2012 John Wiley＆Sons，Ltd。
Code clones are said to threaten the maintainability of a system—especially when the system evolves and source code is changed. Whether clones increase maintenance effort can be analyzed by comparing the stability of cloned code with the stability of non‐cloned code. A previous study found that cloned code is even more stable than non‐cloned code and, thus, may require less maintenance effort—contrary to the frequently voiced assumption. In this paper, we partially replicate this study using a more fine‐grained measurement. We furthermore extend the study to subject systems from academia and industry and evaluate the effect of different clone detection parameters on clone stability and how the stability changes over time. In general, we were able to confirm the findings of the previous study. Nevertheless, our results also show that clone stability varies depending on the clones' characteristics, the corresponding project environment, and over time. Copyright © 2012 John Wiley & Sons, Ltd.