You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: progNav Paper/progNav Paper.tex
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -232,13 +232,13 @@ \section{Flower}
232
232
Flower was designed to realize all of the principles described in Section \ref{DesignPrinciples}.
233
233
We implemented Flower as a plugin to the Eclipse IDE~\cite{Eclipse}.
234
234
We chose Eclipse because it is one of the most widely used open source IDEs for Java development and it provides many extension points for plugins.
235
-
Flower extends \emph{Call Hierarchy}, which allows it to reason about variables that are passed between methods.
235
+
Flower extends \emph{Call Hierarchy}, using its search functionality to track the flow of data across methods.
236
236
Leveraging Eclipse's incremental compiler and JDT core, Flower also implements several AST visitors to detect proper and up-to-date variable references.
237
237
238
238
When active, Flower makes two modifications to Eclipse's user interface.
239
-
First, it highlights on-screen references to selected variables.
240
-
Secondly, when references to the selected variable appear off-screen -- either elsewhere in the current method or in other methods -- Flower adds links to those locations to the code view.
241
-
Figure \ref{fig:tool} depicts Flower invoked on a variable participants were asked to inspect as part of our evaluation. To visualize how a programmer would interact with Flower, consider the following scenario:
239
+
First, it highlights on-screen references to selected variables.
240
+
Secondly, when references to the selected variable appear off-screen -- either elsewhere in the current method or in other methods -- Flower adds links to those locations above and bellow the code view as well as to the code itself.
241
+
Figure \ref{fig:tool} depicts Flower invoked on a variable participants were asked to inspect as part of our evaluation. We also provide a video demonstrating Flower online.\footnote{Screen cast of Flower in action: \url{tinyurl.com/FlowerDemo}} To visualize how a programmer would interact with Flower, consider the following scenario:
242
242
243
243
Suppose you are a programmer and you notice that by tampering with the value of the \texttt{fileName} variable, malicious users could gain access to sensitive information in the database.
244
244
You want to determine whether users can modify \texttt{fileName} before it gets passed into \texttt{parseAndCache}.
0 commit comments