some more steps into exceptions

Author: thomasWeise

bibliography/bibliography.bib

@@ -4,8 +4,12 @@
 %
 \newacronym[description={Artificial Intelligence, see, e.g.,~\cite{RN2022AIAMA}}]{AI}{AI}{Artificial Intelligence}%
 \newacronym[description={Data Science, see, e.g.,~\cite{G2019DSFSFPWP}}]{DS}{DS}{Data Science}%
+\newacronym[description={Garbage In--Garbage Out, see, e.g.,~\cite{PKBCBR2005GIGOAELAOMBEUP}}]{GIGO}{GIGO}{Garbage In--Garbage Out}
 \newacronym[description={Integrated Development Environment, see \gls{ide}}]{IDE}{IDE}{Integrated Development Environment}%
 \newacronym[description={Machine Learning, see, e.g.,~\cite{SSBD2014UMLFTTA}}]{ML}{ML}{Machine Learning}%
 \newacronym[description={Operating System, the system that runs your computer, see, e.g., \linux\ and \windows}]{OS}{OS}{Operating System}%
+\newacronym[description={see \gls{stderrs} and~\cite{J2024PTOGBSI8IS12ESSSSIS}},sort={stderr}]{stderr}{\texttt{stderr}}{standard error stream}%
+\newacronym[description={see \gls{stdins} and~\cite{J2024PTOGBSI8IS12ESSSSIS}},sort={stdin}]{stdin}{\texttt{stdin}}{standard input stream}%
+\newacronym[description={see \gls{stdouts} and~\cite{J2024PTOGBSI8IS12ESSSSIS}},sort={stdout}]{stdout}{\texttt{stdout}}{standard output stream}%
 \newacronym[description={Version Control Systems, see \gls{vcs}}]{VCS}{VCS}{Version Control Systems}%
 %

notation/acronyms.sty

@@ -153,14 +153,43 @@ See \cref{sec:howFloatingPointNumbersWork}.%
 }%
 }%
 %
+\newglossaryentry{stderrs}{%
+name={standard error stream},%
+description={%
+The \acrfull{stderr} is one of the three pre-defined streams of a console process (together with the \gls{stdins} and the \gls{stdouts})~\cite{J2024PTOGBSI8IS12ESSSSIS}. %
+It is the text stream to which the process writes information about errors and exceptions. %
+If an uncaught \pythonilIdx{Exception} is raised in \python\ and the program terminates, then this information is written to \pgls{stderr}. %
+If you run a program in a \pgls{terminal}, then the text that a process writes to its \pgls{stderr} appears in the console.%
+}%
+}%
+%
+\newglossaryentry{stdins}{%
+name={standard input stream},%
+description={%
+The \acrfull{stdin} is one of the three pre-defined streams of a console process (together with the \pgls{stdouts} and the \pgls{stderrs})~\cite{J2024PTOGBSI8IS12ESSSSIS}. %
+It is the text stream from which the process reads its input text, if any. %
+The \python\ instruction \pythonilIdx{input} reads from this stream. %
+If you run a program in a \pgls{terminal}, then the text that you type into the terminal while the process is running appears in this stream.%
+}%
+}%
+%
+\newglossaryentry{stdouts}{%
+name={standard output stream},%
+description={%
+The \acrfull{stdout} is one of the three pre-defined streams of a console process (together with the \pgls{stdins} and the \pgls{stderrs})~\cite{J2024PTOGBSI8IS12ESSSSIS}. %
+It is the text stream to which the process writes its normal output. %
+The \pythonilIdx{print} instruction of \python\ writes text to this stream. %
+If you run a program in a \pgls{terminal}, then the text that a process writes to its \pgls{stdout} appears in the console.%
+}%
+}%
 %
 \newglossaryentry{sudo}{%
 text={\texttt{sudo}},%
 name={sudo},%
 sort={sudo},%
 description={%
 In order to perform administrative tasks such as installing new software under \linux, root (or ``super'') user privileges as needed~\cite{CN2020ULB}. %
-A normal user can execute a program in the \gls{terminal} as super user by pre-pending \bashil{sudo}, often referred to as ``super user do.'' %
+A normal user can execute a program in the \pgls{terminal} as super user by pre-pending \bashil{sudo}, often referred to as ``super user do.'' %
 This requires the root password.%
 }%
 }%
@@ -209,8 +238,8 @@ name={Version Control System},%
 plural={Version Control Systems},%
 description={%
 A \acrfull{VCS} is a software which allows you to manage and preserve the historical development of your program code~\cite{T2024BGAGVCPMATFTND}. %
-A distributed \gls{VCS} allows multiple users to work on the same code and upload their changes to the server, which then preserves the change history.
-The most popular distributed \gls{VCS} is \gls{git}.%
+A distributed \pgls{VCS} allows multiple users to work on the same code and upload their changes to the server, which then preserves the change history.
+The most popular distributed \pgls{VCS} is \pgls{git}.%
 }%
 }%
 %

notation/terms.sty

@@ -247,7 +247,7 @@ breaklines=true%
 %
 $\downarrow$~~\expandafter\bashil{python3 #3}~~$\downarrow$%
 %
-\lstinputlisting[label={exec:#5},style=text_style,caption={The standard output of the program~\href{\csname @pwp@gitUrl:lst:#5\endcsname}{\textil{#3}} given in~\cref{lst:#5}.}]{\csname @pwp@gitFile:exec:#5\endcsname}%
+\lstinputlisting[label={exec:#5},style=text_style,caption={The \gls{stdout} of the program~\href{\csname @pwp@gitUrl:lst:#5\endcsname}{\textil{#3}} given in~\cref{lst:#5}.}]{\csname @pwp@gitFile:exec:#5\endcsname}%
 \end{figure}%
 }%
 %
@@ -275,7 +275,7 @@ $\downarrow$~~\expandafter\bashil{python3 #3}~~$\downarrow$%
 %
 $\downarrow$~~\expandafter\bashil{python3 #3}~~$\downarrow$%
 %
-\lstinputlisting[label={exec:#5},style=text_style,caption={The standard output and error as well as the exit code of the program~\href{\csname @pwp@gitUrl:lst:#5\endcsname}{\textil{#3}} given in~\cref{lst:#5}.}]{\csname @pwp@gitFile:exec:#5\endcsname}%
+\lstinputlisting[label={exec:#5},style=text_style,caption={The \gls{stdout} and \gls{stderr} as well as the exit code of the program~\href{\csname @pwp@gitUrl:lst:#5\endcsname}{\textil{#3}} given in~\cref{lst:#5}.}]{\csname @pwp@gitFile:exec:#5\endcsname}%
 \end{figure}%
 }%
 %

styles/listing.sty

@@ -116,7 +116,7 @@
 \begin{sloppypar}%
 We can use \pythonil{int_var} just like any other value.
 For example, we can compute \pythonil{2 + int_var} and pass the result to the \pythonilIdx{print} function.
-This will then print \pythonil{3} to the standard output of our program.
+This will then print \pythonil{3} to the \pgls{stdout} of our program.
 We can also use \pythonil{int_var} in \pglspl{fstring}\pythonIdx{f-string}\pythonIdx{str!f} about which we leared back in \cref{sec:fstrings}.
 \pythonil{f"int_var has value \{int_var\}."} will render to \pythonil{"int_var has value 1."}.%
 \end{sloppypar}%
@@ -128,7 +128,7 @@
 In this computation, the current (old) value of \pythonil{int_var} is used.
 It therefore corresponds to computing \pythonil{(3 * 1) + 1}, which equals~\pythonil{4}.
 This value is stored somewhere in memory and \pythonil{int_var} points to it.
-Doing \pythonil{print(f"int_var is now \{int_var\}.")} will print \textil{int_var is now 4.} to the standard output.
+Doing \pythonil{print(f"int_var is now \{int_var\}.")} will print \textil{int_var is now 4.} to the \pgls{stdout}.
 The value \pythonil{1} is now no longer referenced.
 Eventually, the \python\ interpreter could free the corresponding memory to use it for something else.
 
@@ -145,7 +145,7 @@
 Finally, \pythonil{print(f"new_var = \{new_var\}." )} then prints \textil{new_var = 14.0.}.%
 \end{sloppypar}%
 %
-The standard output of the complete program is given in \cref{exec:variables:assignment}.
+The \acrfull{stdout} of the complete program is given in \cref{exec:variables:assignment}.
 For your convenience, we also showed the results when executing the program in \pycharm\ or the \ubuntu\ \pgls{terminal} in \cref{fig:variables:assignment}.
 They are obviously identical.
 
@@ -279,10 +279,10 @@
 In each iteration of the approximation, we simply set \pythonil{e *= 2}\pythonIdx{*=}, which is equivalent to \pythonil{e = e * 2}, to double the number of edges.
 We compute \pythonil{s = sqrt(2 - sqrt(4 - (s ** 2)))}\pythonIdx{sqrt} having imported\pythonIdx{import} the \pythonilIdx{sqrt} function from the \pythonilIdx{math} module.
 We print the approximated value of~\numberPi\ as \pythonil{e * s / 2}.
-Notice how elegantly we use the unicode characters~$\pi$ and~$\approx$ via the escapes~\pythonil{\\u03c0} and \pythonil{\\u2248}\pythonIdx{\textbackslash{u}}, respectively, from back in~\cref{sec:unicodeChars} (and how nicely it indeed prints the greek character~$\pi$ in the standard output in \cref{exec:variables:pi_liu_hui}).
+Notice how elegantly we use the unicode characters~$\pi$ and~$\approx$ via the escapes~\pythonil{\\u03c0} and \pythonil{\\u2248}\pythonIdx{\textbackslash{u}}, respectively, from back in~\cref{sec:unicodeChars} (and how nicely it indeed prints the greek character~$\pi$ in the \pgls{stdout} in \cref{exec:variables:pi_liu_hui}).
 Either way, since \cref{eq:liuhui:sidelength,eq:liuhui:approx} are always the same, we can simply copy-paste the lines of code for updating~\pythonil{s}, \pythonil{e}, and printing the approximated value of~\numberPi\ several times.
 
-\Cref{exec:variables:pi_liu_hui} shows the standard output produced by this program.
+\Cref{exec:variables:pi_liu_hui} shows the \acrfull{stdout} produced by this program.
 Indeed, each new approximation comes closer to~\numberPi.
 For 192~edges, we get the approximation~\pythonil{3.1414524722853443}.
 Given that the constant~\pythonilIdx{pi} from the \pythonilIdx{math} module is \pythonil{3.141592653589793}, we find that the first four digits are correct and that the number is only off by only 0.0045\%!