[Commit] mint-2004b intro.tex,1.5,1.6 nickle.tex,1.5,1.6

[Bart Massey]

Committed by: bart

Update of /local/src/CVS/mint-2004b
In directory home.keithp.com:/tmp/cvs-serv30481

Modified Files:
	intro.tex nickle.tex 
Log Message:
Some edits suggested by Keithp.



Index: intro.tex
===================================================================
RCS file: /local/src/CVS/mint-2004b/intro.tex,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- intro.tex	1 Dec 2004 22:31:01 -0000	1.5
+++ intro.tex	2 Dec 2004 02:45:29 -0000	1.6
@@ -12,17 +12,16 @@
 Lex and Yacc~\cite{lexyacc} are both exemplars of and models
 for this approach.
 
-That parser generation is a commonly accepted technique is well evident in
-the relative amount of discussion given by early~\cite{greendragon} and
-newer~\cite{reddragon} (but not new, by any means) compiler construction
-books.  The older text prominantly discusses the relative merits of LL,
-Recursive Descent and machine generated LALR parsers.  However, all of the
-technical focus in the newer generation book is on the back-end -- semantic
-analysis and code generation, the parser itself is passed over quickly in
-the authors haste to get on to something interesting.
-
-One wonders why some authors bother to describe ad-hoc lexing and parsing
-techniques in more recent texts~\cite{fraserhanson}.
+One of the earliest compiler construction
+books~\cite{greendragon} devotes a great deal of attention
+to this topic.  The relative merits of LL, Recursive Descent
+and machine-generated LALR parsers are discussed.  However,
+newer books tend to focus on back-end semantic analysis and
+code generation. The parser itself is passed over quickly,
+in the authors' haste to get on to something interesting.
+Given this ubiquity, it is mildly surprising to find anyone
+still advocating ad hoc lexing and parsing in a standard
+text~\cite{fraserhanson}.
 
 In this environment, constructing yet another parser
 generator requires powerful motivation and careful

Index: nickle.tex
===================================================================
RCS file: /local/src/CVS/mint-2004b/nickle.tex,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- nickle.tex	1 Dec 2004 23:00:41 -0000	1.5
+++ nickle.tex	2 Dec 2004 02:45:29 -0000	1.6
@@ -16,13 +16,11 @@
 generated code to check to make sure the result is also of
 the right type at run-time.
 
-Nickle includes an array of composite data types, from
+Nickle includes a wide range of composite data types, from
 arrays and hash tables to records and tagged unions.  These
-behave much like their C bretheren.  Notable exceptions
-include arrays, which are first-class objects in Nickle.
-Assignment and function parameter passing is done by value:
-reference-typed parameters may be used for efficiency or
-clarity.
+behave much like their C bretheren.  Nickle assignment and
+function parameter passing is done by value: reference-typed
+parameters may be used for efficiency or clarity.
 
 Any non-recursive value within Nickle can be represented within the
 compilation environment as a constant or initializer.  This means that large