arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 1801.01025cs.SE
收藏

流行程序设计语言的缺陷解决特性研究

A Study of Bug Resolution Characteristics in Popular Programming Languages

Jie M. Zhang, Feng Li, Dan Hao, Meng Wang, Hao Tang, Lu Zhang, Mark Harman

摘要:

本文介绍了一项大规模的研究,调查了用不同程序设计语言编写的流行Github项目中的错误解决特征。我们探索相关性,但当然不能推断因果关系。具体来说,我们分析了来自大约7000万个源代码行的错误解决数据,这些数据来自600个GitHub项目的300万次提交,主要是用10种程序设计语言编写的。我们发现明显的错误解决时间和补丁(修复)大小的显着变化。虽然从这种大规模的实证研究结果的解释是固有的困难,我们认为,中位数的差异是足够大,值得进一步调查,复制,重新分析和后续研究。例如,在我们的语料库中,Ruby的明显bug解决时间(从引发到解决的时间)中位数是Go的4倍,Java的2.5倍。我们还发现,对于强类型和静态类型的程序,补丁往往会触及更多的文件。然而,我们也发现了一个较低的解决bug的解决时间的证据提交到静态类型语言构建的项目。这些发现,如果在随后的后续研究中重复,可能会进一步揭示关于静态类型重要性的争论。

英文摘要:

This paper presents a large-scale study that investigates the bug resolution characteristics among popular Github projects written in different programming languages. We explore correlations but, of course, we cannot infer causation. Specifically, we analyse bug resolution data from approximately 70 million Source Line of Code, drawn from 3 million commits to 600 GitHub projects, primarily written in 10 programming languages. We find notable variations in apparent bug resolution time and patch (fix) size. While interpretation of results from such large-scale empirical studies is inherently difficult, we believe that the differences in medians are sufficiently large to warrant further investigation, replication, re-analysis and follow up research. For example, in our corpus, the median apparent bug resolution time (elapsed time from raise to resolve) for Ruby was 4X that for Go and 2.5X for Java. We also found that patches tend to touch more files for the corpus of strongly typed and for statically typed programs. However, we also found evidence for a lower elapsed resolution time for bug resolution committed to projects constructed from statically typed languages. These findings, if replicated in subsequent follow on studies, may shed further empirical light on the debate about the importance of static typing.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑