src/Doc/Isar_Ref/Outer_Syntax.thy
author wenzelm
Sun Oct 18 22:57:09 2015 +0200 (2015-10-18)
changeset 61477 e467ae7aa808
parent 61473 34d1913f0b20
child 61493 0debd22f0c0e
permissions -rw-r--r--
more control symbols;
wenzelm@27037
     1
theory Outer_Syntax
wenzelm@42651
     2
imports Base Main
wenzelm@27037
     3
begin
wenzelm@27037
     4
wenzelm@58618
     5
chapter \<open>Outer syntax --- the theory language \label{ch:outer-syntax}\<close>
wenzelm@27037
     6
wenzelm@58618
     7
text \<open>
wenzelm@27037
     8
  The rather generic framework of Isabelle/Isar syntax emerges from
wenzelm@61477
     9
  three main syntactic categories: \<^emph>\<open>commands\<close> of the top-level
wenzelm@61477
    10
  Isar engine (covering theory and proof elements), \<^emph>\<open>methods\<close> for
wenzelm@27037
    11
  general goal refinements (analogous to traditional ``tactics''), and
wenzelm@61477
    12
  \<^emph>\<open>attributes\<close> for operations on facts (within a certain
wenzelm@27037
    13
  context).  Subsequently we give a reference of basic syntactic
wenzelm@27037
    14
  entities underlying Isabelle/Isar syntax in a bottom-up manner.
wenzelm@27037
    15
  Concrete theory and proof language elements will be introduced later
wenzelm@27037
    16
  on.
wenzelm@27037
    17
wenzelm@61421
    18
  \<^medskip>
wenzelm@61421
    19
  In order to get started with writing well-formed
wenzelm@27037
    20
  Isabelle/Isar documents, the most important aspect to be noted is
wenzelm@61477
    21
  the difference of \<^emph>\<open>inner\<close> versus \<^emph>\<open>outer\<close> syntax.  Inner
wenzelm@27037
    22
  syntax is that of Isabelle types and terms of the logic, while outer
wenzelm@27037
    23
  syntax is that of Isabelle/Isar theory sources (specifications and
wenzelm@27037
    24
  proofs).  As a general rule, inner syntax entities may occur only as
wenzelm@61477
    25
  \<^emph>\<open>atomic entities\<close> within outer syntax.  For example, the string
wenzelm@58724
    26
  @{verbatim \<open>"x + y"\<close>} and identifier @{verbatim z} are legal term
wenzelm@27037
    27
  specifications within a theory, while @{verbatim "x + y"} without
wenzelm@27037
    28
  quotes is not.
wenzelm@27037
    29
wenzelm@27037
    30
  Printed theory documents usually omit quotes to gain readability
wenzelm@27037
    31
  (this is a matter of {\LaTeX} macro setup, say via @{verbatim
wenzelm@60270
    32
  "\\isabellestyle"}, see also @{cite "isabelle-system"}).  Experienced
wenzelm@27037
    33
  users of Isabelle/Isar may easily reconstruct the lost technical
wenzelm@27037
    34
  information, while mere readers need not care about quotes at all.
wenzelm@58618
    35
\<close>
wenzelm@27037
    36
wenzelm@27037
    37
wenzelm@58618
    38
section \<open>Commands\<close>
wenzelm@50213
    39
wenzelm@58618
    40
text \<open>
wenzelm@50213
    41
  \begin{matharray}{rcl}
wenzelm@50213
    42
    @{command_def "print_commands"}@{text "\<^sup>*"} & : & @{text "any \<rightarrow>"} \\
wenzelm@50213
    43
    @{command_def "help"}@{text "\<^sup>*"} & : & @{text "any \<rightarrow>"} \\
wenzelm@50213
    44
  \end{matharray}
wenzelm@50213
    45
wenzelm@55112
    46
  @{rail \<open>
wenzelm@50213
    47
    @@{command help} (@{syntax name} * )
wenzelm@55112
    48
  \<close>}
wenzelm@50213
    49
wenzelm@61439
    50
  \<^descr> @{command "print_commands"} prints all outer syntax keywords
wenzelm@50213
    51
  and commands.
wenzelm@50213
    52
wenzelm@61439
    53
  \<^descr> @{command "help"}~@{text "pats"} retrieves outer syntax
wenzelm@50213
    54
  commands according to the specified name patterns.
wenzelm@58618
    55
\<close>
wenzelm@50213
    56
wenzelm@50213
    57
wenzelm@58618
    58
subsubsection \<open>Examples\<close>
wenzelm@50213
    59
wenzelm@58618
    60
text \<open>Some common diagnostic commands are retrieved like this
wenzelm@58618
    61
  (according to usual naming conventions):\<close>
wenzelm@50213
    62
wenzelm@50213
    63
help "print"
wenzelm@50213
    64
help "find"
wenzelm@50213
    65
wenzelm@50213
    66
wenzelm@58618
    67
section \<open>Lexical matters \label{sec:outer-lex}\<close>
wenzelm@27037
    68
wenzelm@58618
    69
text \<open>The outer lexical syntax consists of three main categories of
wenzelm@28776
    70
  syntax tokens:
wenzelm@28775
    71
wenzelm@61477
    72
  \<^enum> \<^emph>\<open>major keywords\<close> --- the command names that are available
wenzelm@28775
    73
  in the present logic session;
wenzelm@28775
    74
wenzelm@61477
    75
  \<^enum> \<^emph>\<open>minor keywords\<close> --- additional literal tokens required
wenzelm@28775
    76
  by the syntax of commands;
wenzelm@28775
    77
wenzelm@61477
    78
  \<^enum> \<^emph>\<open>named tokens\<close> --- various categories of identifiers etc.
wenzelm@27037
    79
wenzelm@28775
    80
wenzelm@28776
    81
  Major keywords and minor keywords are guaranteed to be disjoint.
wenzelm@28775
    82
  This helps user-interfaces to determine the overall structure of a
wenzelm@28775
    83
  theory text, without knowing the full details of command syntax.
wenzelm@28776
    84
  Internally, there is some additional information about the kind of
wenzelm@28776
    85
  major keywords, which approximates the command type (theory command,
wenzelm@28776
    86
  proof command etc.).
wenzelm@28775
    87
wenzelm@28775
    88
  Keywords override named tokens.  For example, the presence of a
wenzelm@28775
    89
  command called @{verbatim term} inhibits the identifier @{verbatim
wenzelm@58724
    90
  term}, but the string @{verbatim \<open>"term"\<close>} can be used instead.
wenzelm@28775
    91
  By convention, the outer syntax always allows quoted strings in
wenzelm@28775
    92
  addition to identifiers, wherever a named entity is expected.
wenzelm@28775
    93
wenzelm@28776
    94
  When tokenizing a given input sequence, the lexer repeatedly takes
wenzelm@28776
    95
  the longest prefix of the input that forms a valid token.  Spaces,
wenzelm@28776
    96
  tabs, newlines and formfeeds between tokens serve as explicit
wenzelm@28776
    97
  separators.
wenzelm@28776
    98
wenzelm@61421
    99
  \<^medskip>
wenzelm@61421
   100
  The categories for named tokens are defined once and for all as follows.
wenzelm@27037
   101
wenzelm@28776
   102
  \begin{center}
wenzelm@28775
   103
  \begin{supertabular}{rcl}
wenzelm@53059
   104
    @{syntax_def ident} & = & @{text "letter (subscript\<^sup>? quasiletter)\<^sup>*"} \\
wenzelm@28775
   105
    @{syntax_def longident} & = & @{text "ident("}@{verbatim "."}@{text "ident)\<^sup>+"} \\
wenzelm@58724
   106
    @{syntax_def symident} & = & @{text "sym\<^sup>+  |  "}@{verbatim \<open>\\<close>}@{verbatim "<"}@{text ident}@{verbatim ">"} \\
wenzelm@28775
   107
    @{syntax_def nat} & = & @{text "digit\<^sup>+"} \\
wenzelm@40290
   108
    @{syntax_def float} & = & @{syntax_ref nat}@{verbatim "."}@{syntax_ref nat}@{text "  |  "}@{verbatim "-"}@{syntax_ref nat}@{verbatim "."}@{syntax_ref nat} \\
wenzelm@28775
   109
    @{syntax_def var} & = & @{verbatim "?"}@{text "ident  |  "}@{verbatim "?"}@{text ident}@{verbatim "."}@{text nat} \\
wenzelm@28775
   110
    @{syntax_def typefree} & = & @{verbatim "'"}@{text ident} \\
wenzelm@28775
   111
    @{syntax_def typevar} & = & @{verbatim "?"}@{text "typefree  |  "}@{verbatim "?"}@{text typefree}@{verbatim "."}@{text nat} \\
wenzelm@58724
   112
    @{syntax_def string} & = & @{verbatim \<open>"\<close>} @{text "\<dots>"} @{verbatim \<open>"\<close>} \\
wenzelm@28775
   113
    @{syntax_def altstring} & = & @{verbatim "`"} @{text "\<dots>"} @{verbatim "`"} \\
wenzelm@55033
   114
    @{syntax_def cartouche} & = & @{verbatim "\<open>"} @{text "\<dots>"} @{verbatim "\<close>"} \\
wenzelm@58725
   115
    @{syntax_def verbatim} & = & @{verbatim "{*"} @{text "\<dots>"} @{verbatim "*}"} \\[1ex]
wenzelm@28775
   116
wenzelm@58724
   117
    @{text letter} & = & @{text "latin  |  "}@{verbatim \<open>\\<close>}@{verbatim "<"}@{text latin}@{verbatim ">"}@{text "  |  "}@{verbatim \<open>\\<close>}@{verbatim "<"}@{text "latin latin"}@{verbatim ">"}@{text "  |  greek  |"} \\
wenzelm@53059
   118
    @{text subscript} & = & @{verbatim "\<^sub>"} \\
wenzelm@28775
   119
    @{text quasiletter} & = & @{text "letter  |  digit  |  "}@{verbatim "_"}@{text "  |  "}@{verbatim "'"} \\
wenzelm@28775
   120
    @{text latin} & = & @{verbatim a}@{text "  | \<dots> |  "}@{verbatim z}@{text "  |  "}@{verbatim A}@{text "  |  \<dots> |  "}@{verbatim Z} \\
wenzelm@28775
   121
    @{text digit} & = & @{verbatim "0"}@{text "  |  \<dots> |  "}@{verbatim "9"} \\
wenzelm@28775
   122
    @{text sym} & = & @{verbatim "!"}@{text "  |  "}@{verbatim "#"}@{text "  |  "}@{verbatim "$"}@{text "  |  "}@{verbatim "%"}@{text "  |  "}@{verbatim "&"}@{text "  |  "}@{verbatim "*"}@{text "  |  "}@{verbatim "+"}@{text "  |  "}@{verbatim "-"}@{text "  |  "}@{verbatim "/"}@{text "  |"} \\
wenzelm@28775
   123
    & & @{verbatim "<"}@{text "  |  "}@{verbatim "="}@{text "  |  "}@{verbatim ">"}@{text "  |  "}@{verbatim "?"}@{text "  |  "}@{verbatim "@"}@{text "  |  "}@{verbatim "^"}@{text "  |  "}@{verbatim "_"}@{text "  |  "}@{verbatim "|"}@{text "  |  "}@{verbatim "~"} \\
wenzelm@28775
   124
    @{text greek} & = & @{verbatim "\<alpha>"}@{text "  |  "}@{verbatim "\<beta>"}@{text "  |  "}@{verbatim "\<gamma>"}@{text "  |  "}@{verbatim "\<delta>"}@{text "  |"} \\
wenzelm@28775
   125
          &   & @{verbatim "\<epsilon>"}@{text "  |  "}@{verbatim "\<zeta>"}@{text "  |  "}@{verbatim "\<eta>"}@{text "  |  "}@{verbatim "\<theta>"}@{text "  |"} \\
wenzelm@28775
   126
          &   & @{verbatim "\<iota>"}@{text "  |  "}@{verbatim "\<kappa>"}@{text "  |  "}@{verbatim "\<mu>"}@{text "  |  "}@{verbatim "\<nu>"}@{text "  |"} \\
wenzelm@28775
   127
          &   & @{verbatim "\<xi>"}@{text "  |  "}@{verbatim "\<pi>"}@{text "  |  "}@{verbatim "\<rho>"}@{text "  |  "}@{verbatim "\<sigma>"}@{text "  |  "}@{verbatim "\<tau>"}@{text "  |"} \\
wenzelm@28775
   128
          &   & @{verbatim "\<upsilon>"}@{text "  |  "}@{verbatim "\<phi>"}@{text "  |  "}@{verbatim "\<chi>"}@{text "  |  "}@{verbatim "\<psi>"}@{text "  |"} \\
wenzelm@28775
   129
          &   & @{verbatim "\<omega>"}@{text "  |  "}@{verbatim "\<Gamma>"}@{text "  |  "}@{verbatim "\<Delta>"}@{text "  |  "}@{verbatim "\<Theta>"}@{text "  |"} \\
wenzelm@28775
   130
          &   & @{verbatim "\<Lambda>"}@{text "  |  "}@{verbatim "\<Xi>"}@{text "  |  "}@{verbatim "\<Pi>"}@{text "  |  "}@{verbatim "\<Sigma>"}@{text "  |"} \\
wenzelm@28775
   131
          &   & @{verbatim "\<Upsilon>"}@{text "  |  "}@{verbatim "\<Phi>"}@{text "  |  "}@{verbatim "\<Psi>"}@{text "  |  "}@{verbatim "\<Omega>"} \\
wenzelm@28775
   132
  \end{supertabular}
wenzelm@28776
   133
  \end{center}
wenzelm@27037
   134
wenzelm@28778
   135
  A @{syntax_ref var} or @{syntax_ref typevar} describes an unknown,
wenzelm@28778
   136
  which is internally a pair of base name and index (ML type @{ML_type
wenzelm@28778
   137
  indexname}).  These components are either separated by a dot as in
wenzelm@28778
   138
  @{text "?x.1"} or @{text "?x7.3"} or run together as in @{text
wenzelm@28778
   139
  "?x1"}.  The latter form is possible if the base name does not end
wenzelm@28778
   140
  with digits.  If the index is 0, it may be dropped altogether:
wenzelm@28778
   141
  @{text "?x"} and @{text "?x0"} and @{text "?x.0"} all refer to the
wenzelm@28778
   142
  same unknown, with basename @{text "x"} and index 0.
wenzelm@28778
   143
wenzelm@28778
   144
  The syntax of @{syntax_ref string} admits any characters, including
wenzelm@58724
   145
  newlines; ``@{verbatim \<open>"\<close>}'' (double-quote) and ``@{verbatim \<open>\\<close>}''
wenzelm@58724
   146
  (backslash) need to be escaped by a backslash; arbitrary
wenzelm@58724
   147
  character codes may be specified as ``@{verbatim \<open>\\<close>}@{text ddd}'',
wenzelm@27037
   148
  with three decimal digits.  Alternative strings according to
wenzelm@28778
   149
  @{syntax_ref altstring} are analogous, using single back-quotes
wenzelm@28778
   150
  instead.
wenzelm@28778
   151
wenzelm@58725
   152
  The body of @{syntax_ref verbatim} may consist of any text not containing
wenzelm@58725
   153
  ``@{verbatim "*}"}''; this allows to include quotes without further
wenzelm@58725
   154
  escapes, but there is no way to escape ``@{verbatim "*}"}''. Cartouches
wenzelm@58725
   155
  do not have this limitation.
wenzelm@28778
   156
wenzelm@55033
   157
  A @{syntax_ref cartouche} consists of arbitrary text, with properly
wenzelm@55033
   158
  balanced blocks of ``@{verbatim "\<open>"}~@{text "\<dots>"}~@{verbatim
wenzelm@55033
   159
  "\<close>"}''.  Note that the rendering of cartouche delimiters is
wenzelm@55033
   160
  usually like this: ``@{text "\<open> \<dots> \<close>"}''.
wenzelm@55033
   161
wenzelm@28778
   162
  Source comments take the form @{verbatim "(*"}~@{text
wenzelm@28778
   163
  "\<dots>"}~@{verbatim "*)"} and may be nested, although the user-interface
wenzelm@28778
   164
  might prevent this.  Note that this form indicates source comments
wenzelm@28778
   165
  only, which are stripped after lexical analysis of the input.  The
wenzelm@61477
   166
  Isar syntax also provides proper \<^emph>\<open>document comments\<close> that are
wenzelm@28778
   167
  considered as part of the text (see \secref{sec:comments}).
wenzelm@27037
   168
wenzelm@27037
   169
  Common mathematical symbols such as @{text \<forall>} are represented in
wenzelm@27037
   170
  Isabelle as @{verbatim \<forall>}.  There are infinitely many Isabelle
wenzelm@27037
   171
  symbols like this, although proper presentation is left to front-end
wenzelm@58842
   172
  tools such as {\LaTeX} or Isabelle/jEdit.  A list of
wenzelm@47822
   173
  predefined Isabelle symbols that work well with these tools is given
wenzelm@47822
   174
  in \appref{app:symbols}.  Note that @{verbatim "\<lambda>"} does not belong
wenzelm@47822
   175
  to the @{text letter} category, since it is already used differently
wenzelm@58618
   176
  in the Pure term language.\<close>
wenzelm@27037
   177
wenzelm@27037
   178
wenzelm@58618
   179
section \<open>Common syntax entities\<close>
wenzelm@27037
   180
wenzelm@58618
   181
text \<open>
wenzelm@27037
   182
  We now introduce several basic syntactic entities, such as names,
wenzelm@27037
   183
  terms, and theorem specifications, which are factored out of the
wenzelm@27037
   184
  actual Isar language elements to be described later.
wenzelm@58618
   185
\<close>
wenzelm@27037
   186
wenzelm@27037
   187
wenzelm@58618
   188
subsection \<open>Names\<close>
wenzelm@27037
   189
wenzelm@58618
   190
text \<open>Entity @{syntax name} usually refers to any name of types,
wenzelm@61477
   191
  constants, theorems etc.\ that are to be \<^emph>\<open>declared\<close> or
wenzelm@61477
   192
  \<^emph>\<open>defined\<close> (so qualified identifiers are excluded here).  Quoted
wenzelm@27037
   193
  strings provide an escape for non-identifier names or those ruled
wenzelm@58724
   194
  out by outer syntax keywords (e.g.\ quoted @{verbatim \<open>"let"\<close>}).
wenzelm@42596
   195
  Already existing objects are usually referenced by @{syntax
wenzelm@42596
   196
  nameref}.
wenzelm@27037
   197
wenzelm@55112
   198
  @{rail \<open>
wenzelm@42596
   199
    @{syntax_def name}: @{syntax ident} | @{syntax symident} |
wenzelm@42596
   200
      @{syntax string} | @{syntax nat}
wenzelm@27037
   201
    ;
wenzelm@60131
   202
    @{syntax_def par_name}: '(' @{syntax name} ')'
wenzelm@27037
   203
    ;
wenzelm@42596
   204
    @{syntax_def nameref}: @{syntax name} | @{syntax longident}
wenzelm@55112
   205
  \<close>}
wenzelm@58618
   206
\<close>
wenzelm@40296
   207
wenzelm@40296
   208
wenzelm@58618
   209
subsection \<open>Numbers\<close>
wenzelm@40296
   210
wenzelm@58618
   211
text \<open>The outer lexical syntax (\secref{sec:outer-lex}) admits
wenzelm@40296
   212
  natural numbers and floating point numbers.  These are combined as
wenzelm@40296
   213
  @{syntax int} and @{syntax real} as follows.
wenzelm@40296
   214
wenzelm@55112
   215
  @{rail \<open>
wenzelm@42596
   216
    @{syntax_def int}: @{syntax nat} | '-' @{syntax nat}
wenzelm@27037
   217
    ;
wenzelm@42596
   218
    @{syntax_def real}: @{syntax float} | @{syntax int}
wenzelm@55112
   219
  \<close>}
wenzelm@40296
   220
wenzelm@42596
   221
  Note that there is an overlap with the category @{syntax name},
wenzelm@40296
   222
  which also includes @{syntax nat}.
wenzelm@58618
   223
\<close>
wenzelm@27037
   224
wenzelm@27037
   225
wenzelm@58618
   226
subsection \<open>Comments \label{sec:comments}\<close>
wenzelm@27037
   227
wenzelm@58725
   228
text \<open>Large chunks of plain @{syntax text} are usually given @{syntax
wenzelm@58725
   229
  verbatim}, i.e.\ enclosed in @{verbatim "{*"}~@{text "\<dots>"}~@{verbatim "*}"},
wenzelm@58725
   230
  or as @{syntax cartouche} @{text "\<open>\<dots>\<close>"}. For convenience, any of the
wenzelm@58725
   231
  smaller text units conforming to @{syntax nameref} are admitted as well. A
wenzelm@58725
   232
  marginal @{syntax comment} is of the form @{verbatim "--"}~@{syntax text}.
wenzelm@58725
   233
  Any number of these may occur within Isabelle/Isar commands.
wenzelm@27037
   234
wenzelm@55112
   235
  @{rail \<open>
wenzelm@56499
   236
    @{syntax_def text}: @{syntax verbatim} | @{syntax cartouche} | @{syntax nameref}
wenzelm@27037
   237
    ;
wenzelm@42596
   238
    @{syntax_def comment}: '--' @{syntax text}
wenzelm@55112
   239
  \<close>}
wenzelm@58618
   240
\<close>
wenzelm@27037
   241
wenzelm@27037
   242
wenzelm@58618
   243
subsection \<open>Type classes, sorts and arities\<close>
wenzelm@27037
   244
wenzelm@58618
   245
text \<open>
wenzelm@27037
   246
  Classes are specified by plain names.  Sorts have a very simple
wenzelm@27037
   247
  inner syntax, which is either a single class name @{text c} or a
wenzelm@27037
   248
  list @{text "{c\<^sub>1, \<dots>, c\<^sub>n}"} referring to the
wenzelm@27037
   249
  intersection of these classes.  The syntax of type arities is given
wenzelm@27037
   250
  directly at the outer level.
wenzelm@27037
   251
wenzelm@55112
   252
  @{rail \<open>
wenzelm@42596
   253
    @{syntax_def classdecl}: @{syntax name} (('<' | '\<subseteq>') (@{syntax nameref} + ','))?
wenzelm@27037
   254
    ;
wenzelm@42596
   255
    @{syntax_def sort}: @{syntax nameref}
wenzelm@27037
   256
    ;
wenzelm@42596
   257
    @{syntax_def arity}: ('(' (@{syntax sort} + ',') ')')? @{syntax sort}
wenzelm@55112
   258
  \<close>}
wenzelm@58618
   259
\<close>
wenzelm@27037
   260
wenzelm@27037
   261
wenzelm@58618
   262
subsection \<open>Types and terms \label{sec:types-terms}\<close>
wenzelm@27037
   263
wenzelm@58618
   264
text \<open>
wenzelm@27037
   265
  The actual inner Isabelle syntax, that of types and terms of the
wenzelm@27037
   266
  logic, is far too sophisticated in order to be modelled explicitly
wenzelm@27037
   267
  at the outer theory level.  Basically, any such entity has to be
wenzelm@27037
   268
  quoted to turn it into a single token (the parsing and type-checking
wenzelm@27037
   269
  is performed internally later).  For convenience, a slightly more
wenzelm@27037
   270
  liberal convention is adopted: quotes may be omitted for any type or
wenzelm@27037
   271
  term that is already atomic at the outer level.  For example, one
wenzelm@58724
   272
  may just write @{verbatim x} instead of quoted @{verbatim \<open>"x"\<close>}.
wenzelm@27037
   273
  Note that symbolic identifiers (e.g.\ @{verbatim "++"} or @{text
wenzelm@27037
   274
  "\<forall>"} are available as well, provided these have not been superseded
wenzelm@27037
   275
  by commands or other keywords already (such as @{verbatim "="} or
wenzelm@27037
   276
  @{verbatim "+"}).
wenzelm@27037
   277
wenzelm@55112
   278
  @{rail \<open>
wenzelm@42596
   279
    @{syntax_def type}: @{syntax nameref} | @{syntax typefree} |
wenzelm@42596
   280
      @{syntax typevar}
wenzelm@27037
   281
    ;
wenzelm@42596
   282
    @{syntax_def term}: @{syntax nameref} | @{syntax var}
wenzelm@27037
   283
    ;
wenzelm@42596
   284
    @{syntax_def prop}: @{syntax term}
wenzelm@55112
   285
  \<close>}
wenzelm@27037
   286
wenzelm@59853
   287
  Positional instantiations are specified as a sequence of terms, or the
wenzelm@59853
   288
  placeholder ``@{text _}'' (underscore), which means to skip a position.
wenzelm@27037
   289
wenzelm@55112
   290
  @{rail \<open>
wenzelm@42596
   291
    @{syntax_def inst}: '_' | @{syntax term}
wenzelm@27037
   292
    ;
wenzelm@42596
   293
    @{syntax_def insts}: (@{syntax inst} *)
wenzelm@55112
   294
  \<close>}
wenzelm@27037
   295
wenzelm@59853
   296
  Named instantiations are specified as pairs of assignments @{text "v =
wenzelm@59853
   297
  t"}, which refer to schematic variables in some theorem that is
wenzelm@59853
   298
  instantiated. Both type and terms instantiations are admitted, and
wenzelm@59853
   299
  distinguished by the usual syntax of variable names.
wenzelm@59853
   300
wenzelm@59853
   301
  @{rail \<open>
wenzelm@59853
   302
    @{syntax_def named_inst}: variable '=' (type | term)
wenzelm@59853
   303
    ;
wenzelm@59853
   304
    @{syntax_def named_insts}: (named_inst @'and' +)
wenzelm@59853
   305
    ;
wenzelm@59853
   306
    variable: @{syntax name} | @{syntax var} | @{syntax typefree} | @{syntax typevar}
wenzelm@59853
   307
  \<close>}
wenzelm@59853
   308
wenzelm@42596
   309
  Type declarations and definitions usually refer to @{syntax
wenzelm@42596
   310
  typespec} on the left-hand side.  This models basic type constructor
wenzelm@42596
   311
  application at the outer syntax level.  Note that only plain postfix
wenzelm@42596
   312
  notation is available here, but no infixes.
wenzelm@27037
   313
wenzelm@55112
   314
  @{rail \<open>
wenzelm@42596
   315
    @{syntax_def typespec}:
wenzelm@42596
   316
      (() | @{syntax typefree} | '(' ( @{syntax typefree} + ',' ) ')') @{syntax name}
wenzelm@27037
   317
    ;
wenzelm@42705
   318
    @{syntax_def typespec_sorts}:
wenzelm@42596
   319
      (() | (@{syntax typefree} ('::' @{syntax sort})?) |
wenzelm@42596
   320
        '(' ( (@{syntax typefree} ('::' @{syntax sort})?) + ',' ) ')') @{syntax name}
wenzelm@55112
   321
  \<close>}
wenzelm@58618
   322
\<close>
wenzelm@27037
   323
wenzelm@27037
   324
wenzelm@58618
   325
subsection \<open>Term patterns and declarations \label{sec:term-decls}\<close>
wenzelm@28754
   326
wenzelm@58618
   327
text \<open>Wherever explicit propositions (or term fragments) occur in a
wenzelm@42596
   328
  proof text, casual binding of schematic term variables may be given
wenzelm@42596
   329
  specified via patterns of the form ``@{text "(\<IS> p\<^sub>1 \<dots> p\<^sub>n)"}''.
wenzelm@42596
   330
  This works both for @{syntax term} and @{syntax prop}.
wenzelm@28754
   331
wenzelm@55112
   332
  @{rail \<open>
wenzelm@42705
   333
    @{syntax_def term_pat}: '(' (@'is' @{syntax term} +) ')'
wenzelm@28754
   334
    ;
wenzelm@42705
   335
    @{syntax_def prop_pat}: '(' (@'is' @{syntax prop} +) ')'
wenzelm@55112
   336
  \<close>}
wenzelm@28754
   337
wenzelm@61421
   338
  \<^medskip>
wenzelm@61421
   339
  Declarations of local variables @{text "x :: \<tau>"} and
wenzelm@28754
   340
  logical propositions @{text "a : \<phi>"} represent different views on
wenzelm@28754
   341
  the same principle of introducing a local scope.  In practice, one
wenzelm@42596
   342
  may usually omit the typing of @{syntax vars} (due to
wenzelm@28754
   343
  type-inference), and the naming of propositions (due to implicit
wenzelm@28754
   344
  references of current facts).  In any case, Isar proof elements
wenzelm@28754
   345
  usually admit to introduce multiple such items simultaneously.
wenzelm@28754
   346
wenzelm@55112
   347
  @{rail \<open>
wenzelm@42596
   348
    @{syntax_def vars}: (@{syntax name} +) ('::' @{syntax type})?
wenzelm@28754
   349
    ;
wenzelm@42705
   350
    @{syntax_def props}: @{syntax thmdecl}? (@{syntax prop} @{syntax prop_pat}? +)
wenzelm@55112
   351
  \<close>}
wenzelm@28754
   352
wenzelm@28754
   353
  The treatment of multiple declarations corresponds to the
wenzelm@42596
   354
  complementary focus of @{syntax vars} versus @{syntax props}.  In
wenzelm@42596
   355
  ``@{text "x\<^sub>1 \<dots> x\<^sub>n :: \<tau>"}'' the typing refers to all variables, while
wenzelm@42596
   356
  in @{text "a: \<phi>\<^sub>1 \<dots> \<phi>\<^sub>n"} the naming refers to all propositions
wenzelm@42596
   357
  collectively.  Isar language elements that refer to @{syntax vars}
wenzelm@42596
   358
  or @{syntax props} typically admit separate typings or namings via
wenzelm@28754
   359
  another level of iteration, with explicit @{keyword_ref "and"}
wenzelm@28754
   360
  separators; e.g.\ see @{command "fix"} and @{command "assume"} in
wenzelm@28754
   361
  \secref{sec:proof-context}.
wenzelm@59785
   362
wenzelm@59785
   363
  @{rail \<open>
wenzelm@59785
   364
    @{syntax_def "fixes"}:
wenzelm@59785
   365
      ((@{syntax name} ('::' @{syntax type})? @{syntax mixfix}? | @{syntax vars}) + @'and')
wenzelm@59785
   366
    ;
wenzelm@59785
   367
    @{syntax_def "for_fixes"}: (@'for' @{syntax "fixes"})?
wenzelm@59785
   368
  \<close>}
wenzelm@59785
   369
wenzelm@59785
   370
  The category @{syntax "fixes"} is a richer variant of @{syntax vars}: it
wenzelm@59785
   371
  admits specification of mixfix syntax for the entities that are introduced
wenzelm@59785
   372
  into the context. An optional suffix ``@{keyword "for"}~@{text "fixes"}''
wenzelm@59785
   373
  is admitted in many situations to indicate a so-called ``eigen-context''
wenzelm@59785
   374
  of a formal element: the result will be exported and thus generalized over
wenzelm@59785
   375
  the given variables.\<close>
wenzelm@28754
   376
wenzelm@28754
   377
wenzelm@58618
   378
subsection \<open>Attributes and theorems \label{sec:syn-att}\<close>
wenzelm@27037
   379
wenzelm@58618
   380
text \<open>Attributes have their own ``semi-inner'' syntax, in the sense
wenzelm@42596
   381
  that input conforming to @{syntax args} below is parsed by the
wenzelm@28754
   382
  attribute a second time.  The attribute argument specifications may
wenzelm@28754
   383
  be any sequence of atomic entities (identifiers, strings etc.), or
wenzelm@42596
   384
  properly bracketed argument lists.  Below @{syntax atom} refers to
wenzelm@42596
   385
  any atomic entity, including any @{syntax keyword} conforming to
wenzelm@42596
   386
  @{syntax symident}.
wenzelm@27037
   387
wenzelm@55112
   388
  @{rail \<open>
wenzelm@42596
   389
    @{syntax_def atom}: @{syntax nameref} | @{syntax typefree} |
wenzelm@42596
   390
      @{syntax typevar} | @{syntax var} | @{syntax nat} | @{syntax float} |
wenzelm@55045
   391
      @{syntax keyword} | @{syntax cartouche}
wenzelm@27037
   392
    ;
wenzelm@42596
   393
    arg: @{syntax atom} | '(' @{syntax args} ')' | '[' @{syntax args} ']'
wenzelm@27037
   394
    ;
wenzelm@42596
   395
    @{syntax_def args}: arg *
wenzelm@27037
   396
    ;
wenzelm@42596
   397
    @{syntax_def attributes}: '[' (@{syntax nameref} @{syntax args} * ',') ']'
wenzelm@55112
   398
  \<close>}
wenzelm@27037
   399
wenzelm@42596
   400
  Theorem specifications come in several flavors: @{syntax axmdecl}
wenzelm@42596
   401
  and @{syntax thmdecl} usually refer to axioms, assumptions or
wenzelm@42596
   402
  results of goal statements, while @{syntax thmdef} collects lists of
wenzelm@42596
   403
  existing theorems.  Existing theorems are given by @{syntax thmref}
wenzelm@42596
   404
  and @{syntax thmrefs}, the former requires an actual singleton
wenzelm@27037
   405
  result.
wenzelm@27037
   406
wenzelm@27037
   407
  There are three forms of theorem references:
wenzelm@60674
   408
wenzelm@61421
   409
  \<^enum> named facts @{text "a"},
wenzelm@27037
   410
wenzelm@61421
   411
  \<^enum> selections from named facts @{text "a(i)"} or @{text "a(j - k)"},
wenzelm@27037
   412
wenzelm@61421
   413
  \<^enum> literal fact propositions using token syntax @{syntax_ref altstring}
wenzelm@56499
   414
  @{verbatim "`"}@{text "\<phi>"}@{verbatim "`"} or @{syntax_ref cartouche}
wenzelm@56499
   415
  @{text "\<open>\<phi>\<close>"} (see also method @{method_ref fact}).
wenzelm@27037
   416
wenzelm@27037
   417
wenzelm@27037
   418
  Any kind of theorem specification may include lists of attributes
wenzelm@27037
   419
  both on the left and right hand sides; attributes are applied to any
wenzelm@27037
   420
  immediately preceding fact.  If names are omitted, the theorems are
wenzelm@27037
   421
  not stored within the theorem database of the theory or proof
wenzelm@27037
   422
  context, but any given attributes are applied nonetheless.
wenzelm@27037
   423
wenzelm@27037
   424
  An extra pair of brackets around attributes (like ``@{text
wenzelm@27037
   425
  "[[simproc a]]"}'') abbreviates a theorem reference involving an
wenzelm@27037
   426
  internal dummy fact, which will be ignored later on.  So only the
wenzelm@27037
   427
  effect of the attribute on the background context will persist.
wenzelm@27037
   428
  This form of in-place declarations is particularly useful with
wenzelm@27037
   429
  commands like @{command "declare"} and @{command "using"}.
wenzelm@27037
   430
wenzelm@55112
   431
  @{rail \<open>
wenzelm@42596
   432
    @{syntax_def axmdecl}: @{syntax name} @{syntax attributes}? ':'
wenzelm@42596
   433
    ;
wenzelm@60631
   434
    @{syntax_def thmbind}:
wenzelm@60631
   435
      @{syntax name} @{syntax attributes} | @{syntax name} | @{syntax attributes}
wenzelm@60631
   436
    ;
wenzelm@42596
   437
    @{syntax_def thmdecl}: thmbind ':'
wenzelm@27037
   438
    ;
wenzelm@42596
   439
    @{syntax_def thmdef}: thmbind '='
wenzelm@27037
   440
    ;
wenzelm@42596
   441
    @{syntax_def thmref}:
wenzelm@56499
   442
      (@{syntax nameref} selection? | @{syntax altstring} | @{syntax cartouche})
wenzelm@56499
   443
        @{syntax attributes}? |
wenzelm@42596
   444
      '[' @{syntax attributes} ']'
wenzelm@27037
   445
    ;
wenzelm@42596
   446
    @{syntax_def thmrefs}: @{syntax thmref} +
wenzelm@27037
   447
    ;
wenzelm@42596
   448
    selection: '(' ((@{syntax nat} | @{syntax nat} '-' @{syntax nat}?) + ',') ')'
wenzelm@55112
   449
  \<close>}
wenzelm@58618
   450
\<close>
wenzelm@27037
   451
wenzelm@60674
   452
wenzelm@60674
   453
section \<open>Diagnostic commands\<close>
wenzelm@60674
   454
wenzelm@60674
   455
text \<open>
wenzelm@60674
   456
  \begin{matharray}{rcl}
wenzelm@60674
   457
    @{command_def "print_theory"}@{text "\<^sup>*"} & : & @{text "context \<rightarrow>"} \\
wenzelm@61252
   458
    @{command_def "print_definitions"}@{text "\<^sup>*"} & : & @{text "context \<rightarrow>"} \\
wenzelm@60674
   459
    @{command_def "print_methods"}@{text "\<^sup>*"} & : & @{text "context \<rightarrow>"} \\
wenzelm@60674
   460
    @{command_def "print_attributes"}@{text "\<^sup>*"} & : & @{text "context \<rightarrow>"} \\
wenzelm@60674
   461
    @{command_def "print_theorems"}@{text "\<^sup>*"} & : & @{text "context \<rightarrow>"} \\
wenzelm@60674
   462
    @{command_def "find_theorems"}@{text "\<^sup>*"} & : & @{text "context \<rightarrow>"} \\
wenzelm@60674
   463
    @{command_def "find_consts"}@{text "\<^sup>*"} & : & @{text "context \<rightarrow>"} \\
wenzelm@60674
   464
    @{command_def "thm_deps"}@{text "\<^sup>*"} & : & @{text "context \<rightarrow>"} \\
wenzelm@60674
   465
    @{command_def "unused_thms"}@{text "\<^sup>*"} & : & @{text "context \<rightarrow>"} \\
wenzelm@60674
   466
    @{command_def "print_facts"}@{text "\<^sup>*"} & : & @{text "context \<rightarrow>"} \\
wenzelm@60674
   467
    @{command_def "print_term_bindings"}@{text "\<^sup>*"} & : & @{text "context \<rightarrow>"} \\
wenzelm@60674
   468
  \end{matharray}
wenzelm@60674
   469
wenzelm@60674
   470
  @{rail \<open>
wenzelm@60674
   471
    (@@{command print_theory} |
wenzelm@61252
   472
      @@{command print_definitions} |
wenzelm@60674
   473
      @@{command print_methods} |
wenzelm@60674
   474
      @@{command print_attributes} |
wenzelm@60674
   475
      @@{command print_theorems} |
wenzelm@60674
   476
      @@{command print_facts}) ('!'?)
wenzelm@60674
   477
    ;
wenzelm@60674
   478
    @@{command find_theorems} ('(' @{syntax nat}? 'with_dups'? ')')? \<newline> (thm_criterion*)
wenzelm@60674
   479
    ;
wenzelm@60674
   480
    thm_criterion: ('-'?) ('name' ':' @{syntax nameref} | 'intro' | 'elim' | 'dest' |
wenzelm@60674
   481
      'solves' | 'simp' ':' @{syntax term} | @{syntax term})
wenzelm@60674
   482
    ;
wenzelm@60674
   483
    @@{command find_consts} (const_criterion*)
wenzelm@60674
   484
    ;
wenzelm@60674
   485
    const_criterion: ('-'?)
wenzelm@60674
   486
      ('name' ':' @{syntax nameref} | 'strict' ':' @{syntax type} | @{syntax type})
wenzelm@60674
   487
    ;
wenzelm@60674
   488
    @@{command thm_deps} @{syntax thmrefs}
wenzelm@60674
   489
    ;
wenzelm@60674
   490
    @@{command unused_thms} ((@{syntax name} +) '-' (@{syntax name} * ))?
wenzelm@60674
   491
  \<close>}
wenzelm@60674
   492
wenzelm@60674
   493
  These commands print certain parts of the theory and proof context.
wenzelm@60674
   494
  Note that there are some further ones available, such as for the set
wenzelm@60674
   495
  of rules declared for simplifications.
wenzelm@60674
   496
wenzelm@61439
   497
  \<^descr> @{command "print_theory"} prints the main logical content of the
wenzelm@60674
   498
  background theory; the ``@{text "!"}'' option indicates extra verbosity.
wenzelm@60674
   499
wenzelm@61439
   500
  \<^descr> @{command "print_definitions"} prints dependencies of definitional
wenzelm@61252
   501
  specifications within the background theory, which may be constants
wenzelm@61252
   502
  \secref{sec:consts} or types (\secref{sec:types-pure},
wenzelm@61252
   503
  \secref{sec:hol-typedef}); the ``@{text "!"}'' option indicates extra
wenzelm@61252
   504
  verbosity.
wenzelm@61252
   505
wenzelm@61439
   506
  \<^descr> @{command "print_methods"} prints all proof methods available in the
wenzelm@60674
   507
  current theory context; the ``@{text "!"}'' option indicates extra
wenzelm@60674
   508
  verbosity.
wenzelm@60674
   509
wenzelm@61439
   510
  \<^descr> @{command "print_attributes"} prints all attributes available in the
wenzelm@60674
   511
  current theory context; the ``@{text "!"}'' option indicates extra
wenzelm@60674
   512
  verbosity.
wenzelm@60674
   513
wenzelm@61439
   514
  \<^descr> @{command "print_theorems"} prints theorems of the background theory
wenzelm@60674
   515
  resulting from the last command; the ``@{text "!"}'' option indicates
wenzelm@60674
   516
  extra verbosity.
wenzelm@60674
   517
wenzelm@61439
   518
  \<^descr> @{command "print_facts"} prints all local facts of the current
wenzelm@60674
   519
  context, both named and unnamed ones; the ``@{text "!"}'' option indicates
wenzelm@60674
   520
  extra verbosity.
wenzelm@60674
   521
wenzelm@61439
   522
  \<^descr> @{command "print_term_bindings"} prints all term bindings that
wenzelm@60674
   523
  are present in the context.
wenzelm@60674
   524
wenzelm@61439
   525
  \<^descr> @{command "find_theorems"}~@{text criteria} retrieves facts
wenzelm@60674
   526
  from the theory or proof context matching all of given search
wenzelm@60674
   527
  criteria.  The criterion @{text "name: p"} selects all theorems
wenzelm@60674
   528
  whose fully qualified name matches pattern @{text p}, which may
wenzelm@60674
   529
  contain ``@{text "*"}'' wildcards.  The criteria @{text intro},
wenzelm@60674
   530
  @{text elim}, and @{text dest} select theorems that match the
wenzelm@60674
   531
  current goal as introduction, elimination or destruction rules,
wenzelm@60674
   532
  respectively.  The criterion @{text "solves"} returns all rules
wenzelm@60674
   533
  that would directly solve the current goal.  The criterion
wenzelm@60674
   534
  @{text "simp: t"} selects all rewrite rules whose left-hand side
wenzelm@60674
   535
  matches the given term.  The criterion term @{text t} selects all
wenzelm@60674
   536
  theorems that contain the pattern @{text t} -- as usual, patterns
wenzelm@60674
   537
  may contain occurrences of the dummy ``@{text _}'', schematic
wenzelm@60674
   538
  variables, and type constraints.
wenzelm@60674
   539
wenzelm@60674
   540
  Criteria can be preceded by ``@{text "-"}'' to select theorems that
wenzelm@61477
   541
  do \<^emph>\<open>not\<close> match. Note that giving the empty list of criteria
wenzelm@61477
   542
  yields \<^emph>\<open>all\<close> currently known facts.  An optional limit for the
wenzelm@60674
   543
  number of printed facts may be given; the default is 40.  By
wenzelm@60674
   544
  default, duplicates are removed from the search result. Use
wenzelm@60674
   545
  @{text with_dups} to display duplicates.
wenzelm@60674
   546
wenzelm@61439
   547
  \<^descr> @{command "find_consts"}~@{text criteria} prints all constants
wenzelm@60674
   548
  whose type meets all of the given criteria. The criterion @{text
wenzelm@60674
   549
  "strict: ty"} is met by any type that matches the type pattern
wenzelm@60674
   550
  @{text ty}.  Patterns may contain both the dummy type ``@{text _}''
wenzelm@60674
   551
  and sort constraints. The criterion @{text ty} is similar, but it
wenzelm@60674
   552
  also matches against subtypes. The criterion @{text "name: p"} and
wenzelm@60674
   553
  the prefix ``@{text "-"}'' function as described for @{command
wenzelm@60674
   554
  "find_theorems"}.
wenzelm@60674
   555
wenzelm@61439
   556
  \<^descr> @{command "thm_deps"}~@{text "a\<^sub>1 \<dots> a\<^sub>n"}
wenzelm@60674
   557
  visualizes dependencies of facts, using Isabelle's graph browser
wenzelm@60674
   558
  tool (see also @{cite "isabelle-system"}).
wenzelm@60674
   559
wenzelm@61439
   560
  \<^descr> @{command "unused_thms"}~@{text "A\<^sub>1 \<dots> A\<^sub>m - B\<^sub>1 \<dots> B\<^sub>n"}
wenzelm@60674
   561
  displays all theorems that are proved in theories @{text "B\<^sub>1 \<dots> B\<^sub>n"}
wenzelm@60674
   562
  or their parents but not in @{text "A\<^sub>1 \<dots> A\<^sub>m"} or their parents and
wenzelm@60674
   563
  that are never used.
wenzelm@60674
   564
  If @{text n} is @{text 0}, the end of the range of theories
wenzelm@60674
   565
  defaults to the current theory. If no range is specified,
wenzelm@60674
   566
  only the unused theorems in the current theory are displayed.
wenzelm@60674
   567
\<close>
wenzelm@60674
   568
wenzelm@27037
   569
end