some more stuff;
Wed, 06 Mar 2002 14:48:21 +0100
changeset 13027 ddf235f2384a
parent 13026 e45ebbb2e18e
child 13028 81c87faed78b
some more stuff; tuned;
--- a/doc-src/IsarRef/generic.tex	Tue Mar 05 20:55:20 2002 +0100
+++ b/doc-src/IsarRef/generic.tex	Wed Mar 06 14:48:21 2002 +0100
@@ -27,6 +27,7 @@
 \item [$\AXCLASS~c \subseteq \vec c~~axms$] defines an axiomatic type class as
   the intersection of existing classes, with additional axioms holding.  Class
   axioms may not contain more than one type variable.  The class axioms (with
@@ -51,6 +52,7 @@
   as it is already included in the default proof step (of $\PROOFNAME$,
   $\BYNAME$, etc.).  In particular, instantiation of trivial (syntactic)
   classes may be performed by a single ``$\DDOT$'' proof step.
@@ -153,8 +155,8 @@
   \item [$\FIXES{~x::\tau~(mx)}$] declares a local parameter of type $\tau$
     and mixfix annotation $mx$ (both are optional).  The special syntax
-    declaration $(structure)$ means that $x$ may be referenced
-    implicitly in this context. %see also FIXME
+    declaration ``$(structure)$'' means that $x$ may be referenced
+    implicitly in this context.
   \item [$\ASSUMES{a}{\vec\phi}$] introduces local premises, similar to
     $\ASSUMENAME$ within a proof (cf.\ \S\ref{sec:proof-context}).
@@ -343,6 +345,7 @@
   single-step elimination proof, such as ``$\ASSUME{}{x = y}~\HENCE{}{y =
     x}~\DDOT$''.  Note that the very same rules known to $symmetric$ are
   declared as $elim$ at the same time.
@@ -404,7 +407,7 @@
   tagged & : & \isaratt \\
@@ -433,27 +436,39 @@
 \item [$tagged~name~args$ and $untagged~name$] add and remove $tags$ of some
   theorem.  Tags may be any list of strings that serve as comment for some
   tools (e.g.\ $\LEMMANAME$ causes the tag ``$lemma$'' to be added to the
   result).  The first string is considered the tag name, the rest its
   arguments.  Note that untag removes any tags of the same name.
 \item [$THEN~n~a$ and $COMP~n~a$] compose rules.  $THEN$ resolves with the
   $n$-th premise of $a$; the $COMP$ version skips the automatic lifting
   process that is normally intended (cf.\ \texttt{RS} and \texttt{COMP} in
 \item [$where~\vec x = \vec t$] perform named instantiation of schematic
   variables occurring in a theorem.  Unlike instantiation tactics such as
   $rule_tac$ (see \S\ref{sec:tactic-commands}), actual schematic variables
   have to be specified (e.g.\ $\Var{x@3}$).
 \item [$unfolded~\vec a$ and $folded~\vec a$] expand and fold back again the
   given meta-level definitions throughout a rule.
 \item [$standard$] puts a theorem into the standard form of object-rules, just
   as the ML function \texttt{standard} (see \cite[\S5]{isabelle-ref}).
-\item [$elim_format$] turns a destruction rule into elimination rule format;
-  see also the ML function \texttt{make\_elim} (see \cite{isabelle-ref}).
+\item [$elim_format$] turns a destruction rule into elimination rule format,
+  by resolving with the rule $\PROP A \Imp (\PROP A \Imp \PROP B) \Imp \PROP
+  B$.
+  Note that the Classical Reasoner (\S\ref{sec:classical-att}) provides its
+  own version of this operation.
 \item [$no_vars$] replaces schematic variables by free ones; this is mainly
   for tuning output of pretty printed theorems.
@@ -538,30 +553,37 @@
 \item [$rule_tac$ etc.] do resolution of rules with explicit instantiation.
   This works the same way as the ML tactics \texttt{res_inst_tac} etc. (see
   Note that multiple rules may be only given there is no instantiation.  Then
   $rule_tac$ is the same as \texttt{resolve_tac} in ML (see
 \item [$cut_tac$] inserts facts into the proof state as assumption of a
   subgoal, see also \texttt{cut_facts_tac} in \cite[\S3]{isabelle-ref}.  Note
-  that the scope of schematic variables is spread over the main goal statement.
-  Instantiations may be given as well, see also ML tactic
+  that the scope of schematic variables is spread over the main goal
+  statement.  Instantiations may be given as well, see also ML tactic
   \texttt{cut_inst_tac} in \cite[\S3]{isabelle-ref}.
 \item [$thin_tac~\phi$] deletes the specified assumption from a subgoal; note
   that $\phi$ may contain schematic variables.  See also \texttt{thin_tac} in
 \item [$subgoal_tac~\phi$] adds $\phi$ as an assumption to a subgoal.  See
   also \texttt{subgoal_tac} and \texttt{subgoals_tac} in
 \item [$rename_tac~\vec x$] renames parameters of a goal according to the list
   $\vec x$, which refers to the \emph{suffix} of variables.
 \item [$rotate_tac~n$] rotates the assumptions of a goal by $n$ positions:
   from right to left if $n$ is positive, and from left to right if $n$ is
   negative; the default value is $1$.  See also \texttt{rotate_tac} in
 \item [$tactic~text$] produces a proof method from any ML text of type
   \texttt{tactic}.  Apart from the usual ML environment and the current
   implicit theory context, the ML code may refer to the following locally
@@ -604,7 +626,7 @@
-  ('simp' | simpall) ('!' ?) opt? (simpmod * )
+  ('simp' | simpall) ('!' ?) opt? (simpmod *)
   opt: '(' (noasm | noasmsimp | noasmuse) ')'
@@ -822,9 +844,9 @@
-  'blast' ('!' ?) nat? (clamod * )
+  'blast' ('!' ?) nat? (clamod *)
-  ('fast' | 'slow' | 'best' | 'safe' | 'clarify') ('!' ?) (clamod * )
+  ('fast' | 'slow' | 'best' | 'safe' | 'clarify') ('!' ?) (clamod *)
   clamod: (('intro' | 'elim' | 'dest') ('!' | () | '?') | 'del') ':' thmrefs
@@ -866,9 +888,9 @@
-  'auto' '!'? (nat nat)? (clasimpmod * )
+  'auto' '!'? (nat nat)? (clasimpmod *)
-  ('force' | 'clarsimp' | 'fastsimp' | 'slowsimp' | 'bestsimp') '!'? (clasimpmod * )
+  ('force' | 'clarsimp' | 'fastsimp' | 'slowsimp' | 'bestsimp') '!'? (clasimpmod *)
   clasimpmod: ('simp' (() | 'add' | 'del' | 'only') |
@@ -945,6 +967,29 @@
+\subsubsection{Classical operations}\label{sec:classical-att}
+  elim_format & : & \isaratt \\
+  swapped & : & \isaratt \\
+\item [$elim_format$] turns a destruction rule into elimination rule format;
+  this operation is similar to the the intuitionistic version
+  (\S\ref{sec:misc-meth-att}), but each premise of the resulting rule acquires
+  an additional local fact of the negated main thesis -- according to the
+  classical principle $(\neg A \Imp A) \Imp A$.
+\item [$swapped$] turns an introduction rule into an elimination, by resolving
+  with the classical swap principle $(\neg B \Imp A) \Imp (\neg A \Imp B)$.
 \subsection{Proof by cases and induction}\label{sec:cases-induct}
 \subsubsection{Rule contexts}\label{sec:rule-cases}
@@ -970,20 +1015,22 @@
 The $\CASENAME$ command provides a shorthand to refer to certain parts of
 logical context symbolically.  Proof methods may provide an environment of
 named ``cases'' of the form $c\colon \vec x, \vec \phi$.  Then the effect of
-$\CASE{c}$ is exactly the same as $\FIX{\vec x}~\ASSUME{c}{\vec\phi}$.
+``$\CASE{c}$'' is that of ``$\FIX{\vec x}~\ASSUME{c}{\vec\phi}$''; term
+bindings may be covered as well, such as $\Var{case}$.
-It is important to note that $\CASENAME$ does \emph{not} provide any means to
-peek at the current goal state, which is treated as strictly non-observable in
-Isar!  Instead, the cases considered here usually emerge in a canonical way
-from certain pieces of specification that appear in the theory somewhere else
-(e.g.\ in an inductive definition, or recursive function).
+Normally the ``terminology'' of a case value (i.e.\ the parameters $\vec x$)
+are marked as hidden.  Using the alternative form ``$(\CASE{c}~\vec x)$''
+enables proof writers to choose their own naming for the subsequent proof
+It is important to note that $\CASENAME$ does \emph{not} provide direct means
+to peek at the current goal state, which is generally considered
+non-observable in Isar.  The text of the cases basically emerge from standard
+elimination or induction rules, which in turn are derived from previous theory
+specifications in a canonical way (say via $\isarkeyword{inductive}$).
 Named cases may be exhibited in the current proof context only if both the
 proof method and the rules involved support this.  Case names and parameters
 of basic rules may be declared by hand as well, by using appropriate
@@ -999,32 +1046,36 @@
   caseref: nameref attributes?
-  casenames (name + )
+  casenames (name +)
-  'params' ((name * ) + 'and')
+  'params' ((name *) + 'and')
   'consumes' nat?
-%FIXME bug in rail
 \item [$\CASE{c}$] invokes a named local context $c\colon \vec x, \vec \phi$,
   as provided by an appropriate proof method (such as $cases$ and $induct$,
   see \S\ref{sec:cases-induct-meth}).  The command $\CASE{c}$ abbreviates
   $\FIX{\vec x}~\ASSUME{c}{\vec\phi}$.
 \item [$\isarkeyword{print_cases}$] prints all local contexts of the current
   state, using Isar proof language notation.  This is a diagnostic command;
   $undo$ does not apply.
 \item [$case_names~\vec c$] declares names for the local contexts of premises
   of some theorem; $\vec c$ refers to the \emph{suffix} of the list of
 \item [$params~\vec p@1 \dots \vec p@n$] renames the innermost parameters of
   premises $1, \dots, n$ of some theorem.  An empty list of names may be given
   to skip positions, leaving the present parameters unchanged.
   Note that the default usage of case rules does \emph{not} directly expose
   parameters to the proof context (see also \S\ref{sec:cases-induct-meth}).
 \item [$consumes~n$] declares the number of ``major premises'' of a rule,
   i.e.\ the number of facts to be consumed when it is applied by an
   appropriate proof method (cf.\ \S\ref{sec:cases-induct-meth}).  The default
@@ -1036,6 +1087,7 @@
   Note that explicit $consumes$ declarations are only rarely needed; this is
   already taken care of automatically by the higher-level $cases$ and $induct$
   declarations, see also \S\ref{sec:cases-induct-att}.
@@ -1079,6 +1131,7 @@
 \item [$cases~insts~R~ps$] applies method $rule$ with an appropriate case
   distinction theorem, instantiated to the subjects $insts$.  Symbolic case
   names are bound according to the rule's local contexts.
@@ -1131,6 +1184,7 @@
   Additional parameters (including the $open$ option) may be given in the same
   way as for $cases$, see above.
 Above methods produce named local contexts (cf.\ \S\ref{sec:rule-cases}), as
@@ -1204,7 +1258,7 @@
 \item [$\isarkeyword{print_induct_rules}$] prints cases and induct rules for
   sets and types of the current context.
 \item [$cases$ and $induct$] (as attributes) augment the corresponding context
   of rules for reasoning about inductive sets and types, using the
   corresponding methods of the same name.  Certain definitional packages of
--- a/doc-src/IsarRef/logics.tex	Tue Mar 05 20:55:20 2002 +0100
+++ b/doc-src/IsarRef/logics.tex	Wed Mar 06 14:48:21 2002 +0100
@@ -146,10 +146,9 @@
-  splitformat (((name *) + 'and') | ('(' complete ')'))
+  splitformat (((name *) + 'and') | ('(' 'complete' ')'))
@@ -433,7 +432,6 @@
   \isarcmd{primrec} & : & \isartrans{theory}{theory} \\
   \isarcmd{recdef} & : & \isartrans{theory}{theory} \\
   \isarcmd{recdef_tc}^* & : & \isartrans{theory}{proof(prove)} \\
-%  \isarcmd{defer_recdef} & : & \isartrans{theory}{theory} \\  %FIXME
@@ -644,6 +642,48 @@
+\subsection{Generating executable code}
+Isabelle/Pure provides a generic infrastructure to support code generation
+from executable specifications, both functional and relational programs.
+Isabelle/HOL instantiates these mechanisms in a way that is amenable to
+end-user applications.  See \cite{isabelle-HOL} for further information (this
+actually covers the new-style theory format).
+  \isarcmd{generate_code} & : & \isartrans{theory}{theory} \\
+  \isarcmd{consts_code} & : & \isartrans{theory}{theory} \\
+  \isarcmd{types_code} & : & \isartrans{theory}{theory} \\  
+  code & : & \isaratt \\
+  generatecode ( () | '(' name ')') ((name '=' term) +)
+  ;
+  constscode (name ('::' type)? template +)
+  ;
+  typescode (name template +)
+  ;
+  template: '(' string ')'
+  ;
+  'code' (name)?
+  ;
 \subsection{Mixfix syntax for continuous operations}