Edvard K. Karlsen
ABSTRACT
The Lancelot plugin extends the integrated development environment Eclipse with support for finding and fixing 'naming bugs' in Java programs. A naming bug is a mismatch between the name and implementation of a method, in the sense that the pairing of name and implementation do not correspond to the implicit method naming conventions used by many well-known open source applications.
Lancelot has not been presented before, but its theoretical foundations and evaluation have been published. The contribution of the present paper is to present a publicly available tool building on our theory, explain the design of the tool, including some necessary adaptations to the interactive use setting, and report on our experience with it. The source code of Lancelot is available under an open source license.
- K. Beck. Implementation Patterns. Addison-Wesley Professional, 2007. Google Scholar
Digital Library
- C. Fellbaum. WordNet: An Electronic Lexical Database. MIT Press, 1998.Google ScholarCross Ref
- E. W. Høst. Meaningful Method Names. PhD thesis, University of Oslo, 2011. http://urn.nb.no/URN:NBN:no-27629.Google Scholar
- E. W. Høst and B. M. Østvold. Debugging method names. In S. Drossopoulou, editor, Proceedings of the 23rd European Conference on Object-Oriented Programming, volume 5653 of Lecture Notes in Computer Science, pages 294--317. Springer, 2009. Google ScholarDigital Library
- D. Hovemeyer and W. Pugh. Finding bugs is easy. In J. M. Vlissides and D. C. Schmidt, editors, OOPSLA Companion, pages 132--136. ACM, 2004. Google ScholarDigital Library
- D. Lawrie, C. Morrell, H. Feild, and D. Binkley. What's in a name? A study of identifiers. In Proceedings of the 14th International Conference on Program Comprehension (ICPC 2006), 14--16 June 2006, Athens, Greece, pages 3--12. IEEE Computer Society, 2006. Google ScholarDigital Library
- C. D. Manning and H. Schuetze. Foundations of Statistical Natural Language Processing. MIT Press, 1999. Google ScholarDigital Library
- R. C. Martin. Clean Code. Prentice Hall, 2008.Google Scholar
- S. McConnell. Code Complete: A Practical Handbook of Software Construction. Microsoft Press, 2nd edition, 2004. Google ScholarDigital Library
- E. Tempero, C. Anslow, J. Dietrich, T. Han, J. Li, M. Lumpe, H. Melton, and J. Noble. Qualitas corpus: A curated collection of Java code for empirical studies. In 2010 Asia Pacific Software Engineering Conference (APSEC2010), Dec. 2010. Google ScholarDigital Library
Index Terms
- Finding and fixing Java naming bugs with the Lancelot Eclipse plugin
Recommendations
Finding bugs in eclipse
OOPSLA '07: Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companionThis will be a live demonstration of FindBugs, a static analysis bug finding tool, on the current development version of Eclipse 3.4. FindBugs reports issues such as null pointer dereferences, comparing incompatible types with equals, invalid method ...
OpenGL Programming in Java
Released by Sun Microsystems in 2003, Java binding for OpenGL (JOGL;https://jogl.dev.java.net) provides students, scientists, and engineers with a new development environment for studying graphics, performing research, and building applications. In this ...
jStar-eclipse: an IDE for automated verification of Java programs
ESEC/FSE '11: Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineeringjStar is a tool for automatically verifying Java programs. It uses separation logic to support abstract reasoning about object specifications. jStar can verify a number of challenging design patterns, including Subject/Observer, Visitor, Factory and ...
Comments