teaching/scientificComputing
Archived
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

[fixes] some language and spelling fixes

Browse Source
This commit is contained in:
Jan Grewe 2018-02-23 18:07:53 +01:00
parent 01298b95d9
commit 7884e1842b
2 changed files with 14 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
debugging/lecture/debugging.tex
View File

@ -439,11 +439,11 @@ that help to solve the problem.
steps for correctness.
\item Call for help and explain the program to someone else. When you
do this, start at the beginning and walk through the program line by
line. Often it is not necessary that the other person is a
programmer or exactly understands what is going on. Often, it is the
line. Often, it is not necessary that the other person is a
programmer or exactly understands what is going on. Rather, it is the
own reflection on the problem and the chosen approach that helps
finding the bug. (This strategy is also known as \codeterm{Rubber
duck debugging}.
finding the bug (This strategy is also known as \codeterm{Rubber
duck debugging}).
\end{enumerate}
@ -492,15 +492,16 @@ The toolbar of the editor offers now a new set of tools for debugging:
\item \textbf{Step} --- Execute the next command and stop.
\item \textbf{Step in} --- If the next command is a
function call, step into it and stop at the first command.
\item \textbf{Step out} --- If the next command is a function call,
proceed until the called function returns, then stop.
\item \textbf{Step out} --- Suppose you entered a function with
\emph{step in}. \emph{Step out} will continue with the execution and
stop once you are back in the calling function.
\item \textbf{Run to cursor} --- Execute all statements up to the
current cursor position.
\item \textbf{Quit debugging} --- Immediately stop the debugging
session and stop the further code execution.
session and stop further code execution.
\end{enumerate}
The debugger offers some more (advanced) features but the
functionality offered by the basic tools is often enough to debug a program.
functionality offered by the basic tools is often enough to debug a
program.

8
designpattern/lecture/designpattern.tex
View File

@ -1,11 +1,11 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\chapter{Design patterns}
\chapter{Design pattern}
Many code fragments are variations of some basic patterns. These
patterns are used in many different variations in many different
Many code fragments are variations of some basic pattern. These
pattern are used in many different variations in many different
contexts. In this chapter we summarize a few of these \enterm[design
pattern]{design patterns}.
pattern]{design pattern}.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Looping over vector elements}