Interestingly, there are only 187 parameters that have both types of rules, and 79 pairs of these parameter rules are unmatched. By applying PaRu to 9 widely used libraries, we located 5,334 parameters with either document or code rules. Our manual inspection (1) identifies and categorizes rules for the located parameters, and (2) establishes mapping between document and code rules. Our automatic approach-PaRu-locates parameters that have constraints either documented in Javadoc ( i.e., document rules) or implied by source code ( i.e., code rules). To analyze as many parameter rules as possible, we took a hybrid approach that combines automatic localization of constrained parameters with manual inspection. In this paper, we conducted an empirical study to investigate the above-mentioned questions. However, it is still unknown (1) what types of parameter rules there are, and (2) how these rules distribute inside documents and source files. To help developers correctly use library APIs, researchers built tools to mine API parameter rules. If a program inappropriately sets an API parameter, the program may exhibit unexpected runtime behaviors. Developers build programs based on software libraries to reduce coding effort.
0 Comments
Leave a Reply. |