From bd94b1312acab342c73c547825bd596809a6a894 Mon Sep 17 00:00:00 2001 From: Erlend Kristiansen Date: Tue, 8 Apr 2014 14:59:57 +0200 Subject: [PATCH] Thesis: removing/altering some todos --- thesis/master-thesis-erlenkr.tex | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/thesis/master-thesis-erlenkr.tex b/thesis/master-thesis-erlenkr.tex index af466870..e3696b47 100644 --- a/thesis/master-thesis-erlenkr.tex +++ b/thesis/master-thesis-erlenkr.tex @@ -472,7 +472,7 @@ computer programs that are easier to maintain and have code that is easier (and better) understood. \section{Notable contributions to the refactoring literature} -\todoin{Update with more contributions} +\todoin{Thinking Forth?} \begin{description} \item[1992] William F. Opdyke submits his doctoral dissertation called @@ -582,9 +582,6 @@ misleading. One would often be better off with textual extract and paste than using the \refa{Extract Class} refactoring in \name{Eclipse}. When it comes to \name{NetBeans}, it does not even show an attempt on providing this refactoring. -\todoin{Visual Studio (C++/C\#), Smalltalk refactoring browser?, -second refactoring rubicon?} - \section{The relation to design patterns}\label{relationToDesignPatterns} Refactoring and design patterns have at least one thing in common, they are both @@ -1132,7 +1129,6 @@ easily (if at all) observe the \emph{history} of a program. This problem is still open. -\todoin{Write?} \begin{comment} Assuming a sequential (non-concurrent) program: -- 2.43.5