Commit c5348e3a authored by paysan's avatar paysan

Fixes from myself and PhiHo Hoang

parent 49093d25
......@@ -620,7 +620,7 @@ input-process-output designing|)}
\index{I!Information-hiding|(}%
\index{S!Structured programming!information-hiding|(}
In a paper \cite{parnas72} published back in 1972,
Dr. \person{David L. Parnas}%
Dr.\@ \person{David L.\@ Parnas}%
\index{P!Parnas, David} showed
that the criteria for decomposing modules should not be steps in the
process, but rather pieces of information that might possibly change.
......@@ -1491,30 +1491,30 @@ language, if such a thing is possible, will more closely resemble
\begin{references}{99}
\bibitem{dahl72} \person{O.J. Dahl},\person{ E.W. Dijkstra}, and \person{C.A.R. Hoare},
\bibitem{dahl72} \person{O.\@ J.\@ Dahl}, \person{E.\@ W.\@ Dijkstra}, and \person{C.\@ A.\@ R.\@ Hoare},
\emph{Structured Programming,} London, Academic Press, 1972.
\bibitem{wirth71} \person{Niklaus Wirth}, ``Program Development by Stepwise
Refinement,'' \emph{Communications of ACM,} 14, No. 4 (1971), 221-27.
\bibitem{stevens74-1} \person{W.P. Stevens}, \person{G.J. Myers}, and \person{L.L. Constantine},
\bibitem{stevens74-1} \person{W.\@ P.\@ Stevens}, \person{G.\@ J.\@ Myers}, and \person{L.\@ L.\@ Constantine},
``Structured Design,'' \emph{IBM Systems Journal,} Vol. 13, No. 2, 1974.
\bibitem{parnas72} \person{David L. Parnas}, ``On the Criteria To Be Used in
\bibitem{parnas72} \person{David L.\@ Parnas}, ``On the Criteria To Be Used in
Decomposing Systems into Modules,'' \emph{Communications of the ACM,}
December 1972.
\bibitem{liskov75} \person{Barbara H. Liskov} and \person{Stephen N. Zilles},
\bibitem{liskov75} \person{Barbara H.\@ Liskov} and \person{Stephen N.\@ Zilles},
``Specification Techniques for Data Abstractions,'' \emph{IEEE
Transactions on Software Engineering,} March 1975.
\bibitem{parnas79} \person{David L. Parnas}, ``Designing Software for Ease of
\bibitem{parnas79} \person{David L.\@ Parnas}, ``Designing Software for Ease of
Extension and Contraction,'' \emph{IEEE Transactions on Software
Engineering,} March 1979.
\bibitem{shorre71} \person{Dewey Val Shorre}, ``Adding Modules to \Forth{},''
1980 FORML Proceedings, p. 71.
\bibitem{bern83} \person{Mark Bernstein}, ``Programming in the Laboratory,''
unpublished paper, 1983.
\bibitem{bell72} \person{James R. Bell}, ``Threaded Code,'' \emph{Communications
\bibitem{bell72} \person{James R.\@ Bell}, ``Threaded Code,'' \emph{Communications
of ACM,} Vol. 16, No. 6, 370-72.
\bibitem{dewar} \person{Robert B.K. DeWar}, ``Indirect Threaded Code,''
\bibitem{dewar} \person{Robert B.\@ K.\@ DeWar}, ``Indirect Threaded Code,''
\emph{Communications of ACM,} Vol. 18, No. 6, 331.
\bibitem{kogge82} \person{Peter M. Kogge}, ``An Architectural Trail to
\bibitem{kogge82} \person{Peter M.\@ Kogge}, ``An Architectural Trail to
Threaded-Code Systems,'' \emph{Computer,} March, 1982.
\bibitem{dumse} \person{Randy Dumse}, ``The R65F11 \Forth{} Chip,'' \emph{\Forth{}
Dimensions,} Vol. 5, No. 2, p. 25.
......
......@@ -84,7 +84,7 @@ natural system is again studied, and the model is revised.
\wepsfigb{fig2-1}{The iterative approach to the
software development cycle, from ``The \Forth{} Philosophy,''
by \person{Kim Harris}, \emph{Dr. Dobb's Journal.}}%
by \person{Kim Harris}, \emph{Dr.\@ Dobb's Journal.}}%
\index{H!Harris, Kim|)}
The \emph{goal} of the method is to produce a model which accurately
......@@ -1380,7 +1380,7 @@ non-numeric characters to appear.
\begin{tip}
To simplify, take advantage of what's available.
\end{tip}%
\index{L!LaManna, Michael|(}
\index{L!LaManna, Michael|(}%
\begin{interview}
\person{Michael LaManna}, a \Forth{} programmer in Long Island, New York,
comments:
......@@ -1534,7 +1534,7 @@ design!%
\begin{references}{9}
\bibitem{harris81} \person{Kim Harris}, ``The \Forth{} Philosophy,''
\emph{Dr. Dobb's Journal,} Vol. 6, Iss. 9, No. 59 (Sept. 81),
\emph{Dr.\@ Dobb's Journal,} Vol. 6, Iss. 9, No. 59 (Sept. 81),
pp. 6-11.
\bibitem{weinberg80} \person{Victor Weinberg}, \emph{Structured Analysis,}
Englewood Cliffs, N.J.: Prentice-Hall, Inc., 1980.
......
......@@ -556,7 +556,7 @@ word using nested \forthb{IF }\forthb{ELSE }\forthb{THEN}s, like this:
We can solve this problem more elegantly by using a ``case statement.''
Here's the same definition, rewritten using the ``\person{Eaker} case
statement'' format, named after Dr. \person{Charles E. Eaker}, the
statement'' format, named after Dr.\@ \person{Charles E. Eaker}, the
gentleman who proposed it \cite{eaker}.
\begin{Code}
......
......@@ -14,7 +14,7 @@ Single
2 2 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 5
4320 2475 4995 2475 4995 2835 4320 2835 4320 2475
2 2 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 5
2250 2475 3060 2475 3060 2835 2250 2835 2250 2475
2250 2475 3105 2475 3105 2835 2250 2835 2250 2475
2 2 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 5
3240 2475 4095 2475 4095 2835 3240 2835 3240 2475
2 2 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 5
......
......@@ -15,7 +15,7 @@
}%
{\color[rgb]{0,0,0}\put(4321,-1996){\framebox(675,360){}}
}%
{\color[rgb]{0,0,0}\put(2251,-1996){\framebox(810,360){}}
{\color[rgb]{0,0,0}\put(2251,-1996){\framebox(855,360){}}
}%
{\color[rgb]{0,0,0}\put(3241,-1996){\framebox(855,360){}}
}%
......
......@@ -24,17 +24,18 @@ work, but that are also readable, logical, and that express the best
solution in the simplest terms.
Although most of the principles described here can be applied to any
language, I've presented them in the context of \Forth{}. \Forth{} is a
language, an operating system, a set of tools, and a philosophy. It
language, I've presented them in the context of \Forth{}. \Forth{} is
a language, an operating system, a set of tools, and a philosophy. It
is an ideal means for thinking because it corresponds to the way our
minds work. \emph{Thinking \Forth{}} is thinking simple, thinking elegant, thinking
flexible. It is not restrictive, not complicated, not over-general.
You don't have to know \Forth{} to benefit from this book. \emph{Thinking
\Forth{}} synthesizes the \Forth{} approach with many principles taught
by modern computer science. The marriage of \Forth{}'s simplicity with
the traditional disciplines of analysis and style will give you a
new and better way to look at software problems and will be helpful
in all areas of computer application.
minds work. \emph{Thinking \Forth{}} is thinking simple, thinking
elegant, thinking flexible. It is \emph{not} restrictive, \emph{not}
complicated, \emph{not} over-general. You don't have to know \Forth{}
to benefit from this book. \emph{Thinking \Forth{}} synthesizes the
\Forth{} approach with many principles taught by modern computer
science. The marriage of \Forth{}'s simplicity with the traditional
disciplines of analysis and style will give you a new and better way
to look at software problems and will be helpful in all areas of
computer application.
If you want to learn more about \Forth{}, another book of mine,
\emph{Starting \Forth{}}, covers the language aspects of
......@@ -73,11 +74,11 @@ wisdom. Enjoy!
\subsection{Acknowledgments}
Many thanks to all the good people who gave their time and ideas to
this book, including: \person{Charles Moore}, Dr. \person{Mark
this book, including: \person{Charles Moore}, Dr.\@ \person{Mark
Bernstein}, \person{Dave Johnson}, \person{John Teleska},
Dr. \person{Michael Starling}, Dr. \person{Peter Kogge}, \person{Tom
Dr.\@ \person{Michael Starling}, Dr.\@ \person{Peter Kogge}, \person{Tom
Dowling}, \person{Donald Burgess}, \person{Cary Campbell},
Dr. \person{Raymond Dessy}, \person{Michael Ham}, and \person{Kim
Dr.\@ \person{Raymond Dessy}, \person{Michael Ham}, and \person{Kim
Harris}. Another of the interviewees, \person{Michael LaManna}, passed
away while this book was in production. He is deeply missed by those
of us who loved him.
......
......@@ -456,7 +456,7 @@ shadowcolor=lightgrey,shadowsize=3pt,blur=true]{\unhbox\@tempboxa}%
\fontfamily{phv}\selectfont\bfseries\slshape
\parindent 0pt
\vbox{{\advance\textwidth1em\hrule \@height 3pt \@width\textwidth}%
\vspace*{0.2ex}{\advance\textwidth-1em\sloppy\uppercase{#1}}\vspace*{0.2ex}%
\vspace*{0.2ex}{\advance\textwidth-1em\sloppy\MakeUppercase{#1}}\vspace*{0.2ex}%
{\advance\textwidth1em\hrule \@height 3pt \@width\textwidth}}%
\vspace*{100pt}}}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment