summaryrefslogtreecommitdiff
path: root/aied2017/patterns.tex
diff options
context:
space:
mode:
authorTimotej Lazar <timotej.lazar@fri.uni-lj.si>2017-02-07 15:27:49 +0100
committerTimotej Lazar <timotej.lazar@fri.uni-lj.si>2017-02-07 15:27:49 +0100
commit5bb37737d5867e4770251e67dca7cf85b9872d0b (patch)
treeef8ef5e2c66427d9adfcaf388efe20cdb24e9004 /aied2017/patterns.tex
parent2eab11fe49bfa3b065bf178537ac3ff1afc79541 (diff)
Add conclusion
Diffstat (limited to 'aied2017/patterns.tex')
-rw-r--r--aied2017/patterns.tex2
1 files changed, 0 insertions, 2 deletions
diff --git a/aied2017/patterns.tex b/aied2017/patterns.tex
index fe2ae6c..47fc9e2 100644
--- a/aied2017/patterns.tex
+++ b/aied2017/patterns.tex
@@ -175,8 +175,6 @@ The leftmost pattern in Fig.~\ref{fig:sum}, drawn with dotted blue arrows, descr
\noindent
We include such patterns in our feature set to cover the base-case clauses in recursive programs, which often include no variables.
-% TODO move to conclusion
-%While the patterns used in this paper appear to be useful for analyzing Prolog programs, it is likely that other kinds of patterns will be needed for other programming languages. In Python, for example, variables can take on different values and be accessed from many places. This will likely require patterns relating more than two instances of a variable, or multiple variables.
%%% Local Variables:
%%% mode: latex