A Review of Source Code Projections in Integrated Development Environments

Abstract

Abstract-The term Projectional editor is commonly used for tools that can work directly with the program's abstract syntax tree. They are able to provide different views of the program, according to the specific editor used. The ability to look at the program from multiple views is often requested as a mean to simplify program comprehension. During their evolution, the Integrated Development Environments were equipped with tools that provide such possibilities. Many of them already work with the parsed abstract syntax tree of the code and thus can be considered for projections. In this paper we review projections available in 6 widely used IDEs. The review categorizes existing projections and shows that significant number of IDE tools depend on the knowledge of program structure, but also that data from other integrated tools are used to enhance the projections.

Preliminary Report on Empirical Study of Repeated Fragments in Internal Documentation

“…This source file would be transformed to the content presented in Listing 2 3 Java lexical tokens were discarded along with asterisks indicating that following lines are part of JavaDoc (lines are preserved for backtracking to original sources). At the end of each JavaDoc comment we added a randomly generated unique "anchor" (DummyClass.jdoc.6.1394135902525 .0.-2042003928. in the example) that prevented detection of duplicates spanning multiple comments.…”

“…Each sentence in the file was a single token. If we 3 We used underscores here to highlight empty lines.…”

“…P RESERVING and comprehending developer's concerns (intents) in the source code is still a current challenge in software development [1], [2], [3], [4]. In this paper we analyze the internal documentation (source code comments, JavaDoc, etc.)…”