# HG changeset patch # User Adam Chlipala # Date 1333307684 14400 # Node ID 9e47cdd76bb566acb6be014c56dfb5083dad0e81 # Parent d5112c099fbf62d3321e9c1c8c82e4d00cb7776d Typo fixes diff -r d5112c099fbf -r 9e47cdd76bb5 src/Intro.v --- a/src/Intro.v Sun Apr 01 15:02:32 2012 -0400 +++ b/src/Intro.v Sun Apr 01 15:14:44 2012 -0400 @@ -177,7 +177,7 @@ (** To make it possible to start from fancy proof automation, rather than working up to it, I have included with the book source a library of %\emph{%##tactics##%}%, or programs that find proofs, since the built-in Coq tactics do not support a high enough level of automation. I use these tactics even from the first chapter with code examples. -Some readers have asked about the pragmatics of using this tactic library in their own developments. My position there is that this tactic library was designed with the specific examples of the book in mind; I do not recommend using it in other settings. Part III should impart the necessary skills to reimplement these tactics and beyond. One generally deals with undecidable problems in interactive theorem proving, so there can be no tactic that solves all goals, though the %\index{tactics!crush}%[crush] tactic that we will meet soon may sometimes feel like that! There are still very useful tricks found in the implementations of [crush] and its cousins, so it may be useful to examine the commented source file %\texttt{%##CpdtTactics.v#.#%}.~\footnote{It's not actually commented yet. \texttt{;-)}}% I implement a new tactic library for each new project, since each project involves a different mix of undecidable theories where a different set of heuristics turns out to work well; and that is what I recommend others do, too. +Some readers have asked about the pragmatics of using this tactic library in their own developments. My position there is that this tactic library was designed with the specific examples of the book in mind; I do not recommend using it in other settings. Part III should impart the necessary skills to reimplement these tactics and beyond. One generally deals with undecidable problems in interactive theorem proving, so there can be no tactic that solves all goals, though the %\index{tactics!crush}%[crush] tactic that we will meet soon may sometimes feel like that! There are still very useful tricks found in the implementations of [crush] and its cousins, so it may be useful to examine the commented source file %\texttt{%##CpdtTactics.v#.#%}.\footnote{It's not actually commented yet. \texttt{;-)}}% I implement a new tactic library for each new project, since each project involves a different mix of undecidable theories where a different set of heuristics turns out to work well; and that is what I recommend others do, too. *) (** ** Installation and Emacs Set-Up *) @@ -247,7 +247,7 @@ \hline Proving in the Large & \texttt{Large.v} \\ \hline -A Taste of Reasoning About Programming Language Syntax & \texttt{Large.v} \\ +A Taste of Reasoning About Programming Language Syntax & \texttt{ProgLang.v} \\ \hline \end{tabular} \end{center}