doc-src/IsarImplementation/Thy/unused.thy
author wenzelm
Fri Sep 01 20:44:16 2006 +0200 (2006-09-01 ago)
changeset 20460 351c63bb2704
parent 20429 116255c9209b
child 20470 c839b38a1f32
permissions -rw-r--r--
tuned;
     1 
     2 text {*
     3 
     4   @{index_ML Variable.trade: "Proof.context -> (thm list -> thm list) -> thm list -> thm list"} \\
     5 
     6 
     7 
     8   \item @{ML Variable.trade} composes @{ML Variable.import} and @{ML
     9   Variable.export}, i.e.\ it provides a view on facts with all
    10   variables being fixed in the current context.
    11 
    12 
    13   In practice, super-contexts emerge either by merging existing ones,
    14   or by adding explicit declarations.  For example, new theories are
    15   usually derived by importing existing theories from the library
    16   @{text "\<Theta> = \<Theta>\<^sub>1 + \<dots> + \<Theta>\<^isub>n"}, or 
    17 
    18 
    19 
    20   The Isar toplevel works differently for interactive developments
    21   vs.\ batch processing of theory sources.  For example, diagnostic
    22   commands produce a warning batch mode, because they are considered
    23   alien to the final theory document being produced eventually.
    24   Moreover, full @{text undo} with intermediate checkpoints to protect
    25   against destroying theories accidentally are limited to interactive
    26   mode.  In batch mode there is only a single strictly linear stream
    27   of potentially desctructive theory transformations.
    28 
    29   \item @{ML Toplevel.empty} is an empty transition; the Isar command
    30   dispatcher internally applies @{ML Toplevel.name} (for the command)
    31   name and @{ML Toplevel.position} for the source position.
    32 
    33 *}
    34