doc-src/IsarImplementation/Thy/unused.thy
changeset 20429 116255c9209b
parent 18537 2681f9e34390
child 20460 351c63bb2704
     1.1 --- a/doc-src/IsarImplementation/Thy/unused.thy	Tue Aug 29 14:31:15 2006 +0200
     1.2 +++ b/doc-src/IsarImplementation/Thy/unused.thy	Tue Aug 29 18:49:33 2006 +0200
     1.3 @@ -1,5 +1,12 @@
     1.4  
     1.5  text {*
     1.6 +  In practice, super-contexts emerge either by merging existing ones,
     1.7 +  or by adding explicit declarations.  For example, new theories are
     1.8 +  usually derived by importing existing theories from the library
     1.9 +  @{text "\<Theta> = \<Theta>\<^sub>1 + \<dots> + \<Theta>\<^isub>n"}, or 
    1.10 +
    1.11 +
    1.12 +
    1.13    The Isar toplevel works differently for interactive developments
    1.14    vs.\ batch processing of theory sources.  For example, diagnostic
    1.15    commands produce a warning batch mode, because they are considered
    1.16 @@ -8,9 +15,10 @@
    1.17    against destroying theories accidentally are limited to interactive
    1.18    mode.  In batch mode there is only a single strictly linear stream
    1.19    of potentially desctructive theory transformations.
    1.20 -*}
    1.21  
    1.22    \item @{ML Toplevel.empty} is an empty transition; the Isar command
    1.23    dispatcher internally applies @{ML Toplevel.name} (for the command)
    1.24    name and @{ML Toplevel.position} for the source position.
    1.25  
    1.26 +*}
    1.27 +