forked from ChrisMayfield/ThinkJava2
-
Notifications
You must be signed in to change notification settings - Fork 0
/
ch00.tex
241 lines (152 loc) · 12.1 KB
/
ch00.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
\chapter*{Preface}
\markboth{PREFACE}{PREFACE}
\addcontentsline{toc}{chapter}{Preface}
{\it Think Java} is an introduction to computer science and programming intended for readers with little or no experience.
We start with the most basic concepts and are careful to define all terms when they are first used.
The book presents each new idea in a logical progression.
Larger topics, like control flow statements and object-oriented programming, are divided into smaller examples and introduced over the course of several chapters.
This book is intentionally concise.
Each chapter is 12--14 pages and covers the material for one week of a college course.
It is not meant to be a comprehensive presentation of Java, but rather, an initial exposure to programming constructs and techniques.
We begin with small problems and basic algorithms and work up to object-oriented design.
In the vocabulary of computer science pedagogy, this book uses the ``objects late'' approach.
\section*{The philosophy behind the book}
Here are the guiding principles that make the book the way it is:
\begin{itemize}
\item {\em One concept at a time.}
We break down topics that give beginners trouble into a series of small steps, so that they can exercise each new concept in isolation before continuing.
\item {\em Balance of Java and concepts.}
The book is not primarily about Java; it uses code examples to demonstrate computer science.
Most chapters start with language features and end with concepts.
\item {\em Conciseness.}
An important goal of the book is to be small enough so that students can read and understand the entire text in a one-semester college or AP course.
%Students can read 1--2 chapters per week, depending on the pace of the instruction.
\item {\em Emphasis on vocabulary.}
We try to introduce the minimum number of terms and define them carefully when they are first used.
We also organize them in glossaries at the end of each chapter.
\item {\em Program development.}
There are many strategies for writing programs, including bottom-up, top-down, and others.
We demonstrate multiple program development techniques, allowing readers to choose methods that work best for them.
\item {\em Multiple learning curves.}
To write a program, you have to understand the algorithm, know the programming language, and be able to debug errors.
We discuss these and other aspects throughout the book, and include an appendix that summarizes our advice.
%\item {\em Spiral approach.}
%Some concepts take time to sink in.
%The more difficult ideas in the book, like recursion, appear several times.
%By coming back to these topics, we give learners a chance to review and reinforce.
%\item {\em Keep it simple.}
%We use the minimum amount of Java to get the maximum amount of programming ability.
%The goal of this book is to teach fundamental ideas from computer science, not Java.
%We leave out some language features, like the \java{switch} statement, that are unnecessary, and we present only a few of the many classes in the Java libraries.
\end{itemize}
\section*{Object-oriented programming}
Some Java books introduce classes and objects immediately; others begin with procedural programming and transition to object-oriented more gradually.
Many of Java's object-oriented features are motivated by problems with previous languages, and their implementations are influenced by this history.
Some of these features are hard to explain when people aren't familiar with the problems they solve.
We get to object-oriented programming as quickly as possible (beginning with Chapter~\ref{immutable}).
But we introduce concepts one at a time, as clearly as possible, in a way that allows readers to practice each idea in isolation before moving on.
So it takes some time to get there.
You can't write Java programs (even hello world) without encountering object-oriented features.
In some cases we explain a feature briefly when it first appears, and then explain it more deeply later on.
This book is well suited to prepare students for the AP Computer Science A exam, which includes object-oriented design and implementation.
(AP is a registered trademark of the College Board.)
We introduce nearly every topic in the ``AP Java subset'' with a few exceptions.
A mapping of {\it Think Java} section numbers to the current AP course description is available on our website: \url{http://thinkjava.org/}.
\section*{Changes to the 2nd edition}
This new edition is three years in the making, with feedback from dozens of instructors and hundreds of students.
A complete history of all changes is available on GitHub.
Here are some of the highlights:
\begin{description}
\item[Chapters 1--4:]
We reordered the material in Chapter~1 to present a more interesting balance of theory and practice.
Chapters 2--3 are much cleaner now too.
Methods are now presented in a single chapter, along with additional in-depth examples.
\item[Chapters 5--8:]
These chapters received the most attention.
We rearranged the content, added many examples and new figures, and removed unnecessary details.
Strings are covered earlier (before arrays) so that readers can apply them to loop problems.
The material on recursion is now a chapter, and we added new sections to explain binary numbers and CodingBat problems.
\item[Chapters 9--12:]
Our main goal for these chapters was to provide better explanations and more diagrams.
Chapters~9 and 10 focus more on immutable vs mutable objects, and we added new sections on BigInteger and StringBuilder.
The other content is largely the same, but it should be easier to understand now.
\item[Chapters 13--16:]
We balanced the amount of content in Chapters~13--14 by moving ArrayLists earlier, and we implement the ``War'' card game as another example.
Chapters~15--16 are brand new in this edition, and they cover more advanced topics including interfaces, polymorphism, and multi-dimensional arrays.
\item[Appendixes:]
We added Appendix~\ref{javadoc} to explain documentation comments and Javadoc in more detail.
%Most of the examples in the chapters do not include documentation comments to save space.
The other three appendixes that were present in the first edition have been revised for clarity and layout.
\end{description}
\section*{About the appendixes}
The chapters of this book are meant to be read in order, because each one builds on the previous one.
We also include several appendixes with material that can be read at any time:
\begin{description}
\item{\bf Appendix A: Tools}
This appendix explains how to download and install Java so you can compile programs on your computer.
It also provides a brief introduction to DrJava -- an ``integrated development environment'' (IDE) that is designed primarily for students -- and other development tools, including Checkstyle for code quality and JUnit for testing.
\item{\bf Appendix B: Javadoc}
It's important to document your classes and methods so that other programmers (including yourself in the future) will know how to use them.
This appendix explains how to read documentation, how to write documentation, and how to use the Javadoc tool.
\item{\bf Appendix C: Graphics}
Java provides libraries for working with graphics and animation, and these topics can be engaging for students.
The libraries require object-oriented features that students will not completely understand until after Chapter~\ref{mutable}, but they can be used much earlier.
\item{\bf Appendix D: Debugging}
We provide debugging suggestions throughout the book, but we also have an appendix with many more suggestions on how to debug your programs.
We recommend that readers review this appendix frequently as they work through the book.
\item{\bf Appendix E: Extras}
With each new edition, we add new material, remove old material, and revise everything else.
Some of the old material may still be useful, so rather than delete it, we moved it to this appendix.
\end{description}
\section*{Using the code examples}
\label{code}
Most of the code examples in this book are available from a Git repository at \url{https://github.com/ChrisMayfield/ThinkJavaCode2}.
Git is a ``version control system'' that allows you to keep track of the files that make up a project.
A collection of files under Git's control is called a ``repository''.
\index{repository}
\index{GitHub}
GitHub is a hosting service that provides storage for Git repositories and a convenient web interface.
It provides several ways to work with the code:
\begin{itemize}
\item You can create a copy of the repository on GitHub by pressing the {\sf Fork} button.
If you don't already have a GitHub account, you'll need to create one.
After forking, you'll have your own repository on GitHub that you can use to keep track of code you write.
Then you can ``clone'' the repository, which downloads a copy of the files to your computer.
\item Alternatively, you could clone the original repository without forking.
If you choose this option, you don't need a GitHub account, but you won't be able to save your changes on GitHub.
\item If you don't want to use Git at all, you can download the code in a ZIP archive using the {\sf Download ZIP} button on the GitHub page, or this link: \url{http://tinyurl.com/ThinkJavaCode2}.
\end{itemize}
After you clone the repository or unzip the ZIP file, you should have a directory named {\tt ThinkJavaCode2} with a subdirectory for each chapter in the book.
All examples in this book were developed and tested using Java SE Development Kit 8.
If you are using a more recent version, the examples in this book should still work.
If you are using an older version, some of them may not.
\section*{Contributors over the years}
Many people have sent corrections and suggestions, and we appreciate their valuable feedback!
This list begins with Version 4.0 of the open-source edition, so it omits those who contributed to earlier versions.
\begin{itemize}
\item Ellen Hildreth used this book to teach Data Structures at Wellesley College and submitted a whole stack of corrections, along with some great suggestions.
\item Tania Passfield pointed out that some glossaries had leftover terms that no longer appeared in the text.
\item Elizabeth Wiethoff noticed that the series expansion of $\exp(-x^2)$ was wrong.
She has also worked on a Ruby version of the book.
\item Matt Crawford sent in a whole patch file full of corrections.
\item Chi-Yu Li pointed out a typo and an error in one of the code examples.
\item Doan Thanh Nam corrected an example.
\item Muhammad Saied translated the book into Arabic, and found several errors in the process.
\item Marius Margowski found an inconsistency in a code example.
\item Leslie Klein discovered another error in the series expansion of $\exp(-x^2)$, identified typos in the card array figures, and gave helpful suggestions to clarify several exercises.
\item Micah Lindstrom reported half a dozen typos and sent corrections.
\item James Riely ported the textbook source from LaTeX to Sphinx.
\\ \url{http://fpl.cs.depaul.edu/jriely/thinkapjava/}
\item Peter Knaggs ported the book to C\#.
\\ \url{http://www.rigwit.co.uk/think/sharp/}
\item Heidi Gentry-Kolen recorded several video lectures that follow the book.
\\ \url{https://www.youtube.com/user/digipipeline}
\item Waldo Ribeiro submitted a pull request that corrected a dozen typos.
\end{itemize}
We are especially grateful to the technical reviewers of the O'Reilly Media first edition: Blythe Samuels, David Wisneski, and Stephen Rose.
They found errors, made many great suggestions, and helped make the book much better.
Many students have given exceptional feedback, including Ian Staton, Tanner Wernecke, Jacob Green, Rasha Abuhantash, Nick Duncan, Kylie Davidson, Shirley Jiang, Elena Trafton, Jennifer Gregorio, and Azeem Mufti.
Other contributors who found one or more typos: Stijn Debrouwere, Guy Driesen, Andai Velican, Chris Kuszmaul, Daniel Kurikesu, Josh Donath, Rens Findhammer, Elisa Abedrapo, Yousef BaAfif, Bruce Hill, Matt Underwood, Isaac Sultan, Dan Rice, Robert Beard, Daniel Pierce, Michael Giftthaler, Chris Fox, Min Zeng, and Markus Geuss.
%\medskip
If you have additional comments or ideas about the text, please send them to: \href{mailto:[email protected]}{\tt [email protected]}.
Allen Downey and Chris Mayfield