4
+ − 1
theory Parsing
121
+ − 2
imports Base "Package/Simple_Inductive_Package"
4
+ − 3
begin
+ − 4
42
+ − 5
4
+ − 6
chapter {* Parsing *}
+ − 7
+ − 8
text {*
+ − 9
38
+ − 10
Isabelle distinguishes between \emph{outer} and \emph{inner} syntax.
+ − 11
Theory commands, such as \isacommand{definition}, \isacommand{inductive} and so
+ − 12
on, belong to the outer syntax, whereas items inside double quotation marks, such
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 13
as terms, types and so on, belong to the inner syntax. For parsing inner syntax,
156
+ − 14
Isabelle uses a rather general and sophisticated algorithm, which
38
+ − 15
is driven by priority grammars. Parsers for outer syntax are built up by functional
+ − 16
parsing combinators. These combinators are a well-established technique for parsing,
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 17
which has, for example, been described in Paulson's classic ML-book \cite{paulson-ml2}.
42
+ − 18
Isabelle developers are usually concerned with writing these outer syntax parsers,
193
+ − 19
either for new definitional packages or for calling methods with specific arguments.
42
+ − 20
+ − 21
\begin{readmore}
+ − 22
The library
50
+ − 23
for writing parser combinators is split up, roughly, into two parts.
38
+ − 24
The first part consists of a collection of generic parser combinators defined
+ − 25
in the structure @{ML_struct Scan} in the file
+ − 26
@{ML_file "Pure/General/scan.ML"}. The second part of the library consists of
+ − 27
combinators for dealing with specific token types, which are defined in the
+ − 28
structure @{ML_struct OuterParse} in the file
+ − 29
@{ML_file "Pure/Isar/outer_parse.ML"}.
42
+ − 30
\end{readmore}
38
+ − 31
+ − 32
*}
+ − 33
49
+ − 34
section {* Building Generic Parsers *}
38
+ − 35
+ − 36
text {*
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 37
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 38
Let us first have a look at parsing strings using generic parsing combinators.
108
8bea3f74889d
added to the tactical chapter; polished; added the tabularstar environment (which is just tabular*)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 39
The function @{ML "$$"} takes a string as argument and will ``consume'' this string from
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 40
a given input list of strings. ``Consume'' in this context means that it will
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 41
return a pair consisting of this string and the rest of the input list.
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 42
For example:
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 43
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 44
@{ML_response [display,gray] "($$ \"h\") (explode \"hello\")" "(\"h\", [\"e\", \"l\", \"l\", \"o\"])"}
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 45
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 46
@{ML_response [display,gray] "($$ \"w\") (explode \"world\")" "(\"w\", [\"o\", \"r\", \"l\", \"d\"])"}
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 47
149
+ − 48
The function @{ML "$$"} will either succeed (as in the two examples above) or raise the exception
58
+ − 49
@{text "FAIL"} if no string can be consumed. For example trying to parse
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 50
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 51
@{ML_response_fake [display,gray] "($$ \"x\") (explode \"world\")"
41
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 52
"Exception FAIL raised"}
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 53
58
+ − 54
will raise the exception @{text "FAIL"}.
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 55
There are three exceptions used in the parsing combinators:
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 56
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 57
\begin{itemize}
58
+ − 58
\item @{text "FAIL"} is used to indicate that alternative routes of parsing
41
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 59
might be explored.
58
+ − 60
\item @{text "MORE"} indicates that there is not enough input for the parser. For example
+ − 61
in @{text "($$ \"h\") []"}.
60
5b9c6010897b
doem tuning and made the cookbook work again with recent changes (CookBook/Package/Ind_Interface.thy needs to be looked at to see what the problem with the new parser type is)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 62
\item @{text "ABORT"} is the exception that is raised when a dead end is reached.
108
8bea3f74889d
added to the tactical chapter; polished; added the tabularstar environment (which is just tabular*)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 63
It is used for example in the function @{ML "!!"} (see below).
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 64
\end{itemize}
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 65
50
+ − 66
However, note that these exceptions are private to the parser and cannot be accessed
49
+ − 67
by the programmer (for example to handle them).
+ − 68
108
8bea3f74889d
added to the tactical chapter; polished; added the tabularstar environment (which is just tabular*)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 69
Slightly more general than the parser @{ML "$$"} is the function @{ML
49
+ − 70
Scan.one}, in that it takes a predicate as argument and then parses exactly
52
+ − 71
one item from the input list satisfying this predicate. For example the
58
+ − 72
following parser either consumes an @{text [quotes] "h"} or a @{text
49
+ − 73
[quotes] "w"}:
41
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 74
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 75
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 76
@{ML_response [display,gray]
40
+ − 77
"let
+ − 78
val hw = Scan.one (fn x => x = \"h\" orelse x = \"w\")
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 79
val input1 = (explode \"hello\")
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 80
val input2 = (explode \"world\")
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 81
in
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 82
(hw input1, hw input2)
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 83
end"
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 84
"((\"h\", [\"e\", \"l\", \"l\", \"o\"]),(\"w\", [\"o\", \"r\", \"l\", \"d\"]))"}
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 85
220
+ − 86
Two parsers can be connected in sequence by using the function @{ML "--"}.
+ − 87
For example parsing @{text "h"}, @{text "e"} and @{text "l"} (in this
+ − 88
order) you can achieve by:
38
+ − 89
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 90
@{ML_response [display,gray] "(($$ \"h\") -- ($$ \"e\") -- ($$ \"l\")) (explode \"hello\")"
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 91
"(((\"h\", \"e\"), \"l\"), [\"l\", \"o\"])"}
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 92
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 93
Note how the result of consumed strings builds up on the left as nested pairs.
38
+ − 94
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 95
If, as in the previous example, you want to parse a particular string,
128
+ − 96
then you should use the function @{ML Scan.this_string}:
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 97
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 98
@{ML_response [display,gray] "Scan.this_string \"hell\" (explode \"hello\")"
65
+ − 99
"(\"hell\", [\"o\"])"}
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 100
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 101
Parsers that explore alternatives can be constructed using the function @{ML
220
+ − 102
"||"}. The parser @{ML "(p || q)" for p q} returns the
58
+ − 103
result of @{text "p"}, in case it succeeds, otherwise it returns the
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 104
result of @{text "q"}. For example:
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 105
38
+ − 106
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 107
@{ML_response [display,gray]
40
+ − 108
"let
+ − 109
val hw = ($$ \"h\") || ($$ \"w\")
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 110
val input1 = (explode \"hello\")
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 111
val input2 = (explode \"world\")
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 112
in
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 113
(hw input1, hw input2)
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 114
end"
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 115
"((\"h\", [\"e\", \"l\", \"l\", \"o\"]), (\"w\", [\"o\", \"r\", \"l\", \"d\"]))"}
38
+ − 116
108
8bea3f74889d
added to the tactical chapter; polished; added the tabularstar environment (which is just tabular*)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 117
The functions @{ML "|--"} and @{ML "--|"} work like the sequencing function
50
+ − 118
for parsers, except that they discard the item being parsed by the first (respectively second)
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 119
parser. For example:
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 120
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 121
@{ML_response [display,gray]
40
+ − 122
"let
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 123
val just_e = ($$ \"h\") |-- ($$ \"e\")
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 124
val just_h = ($$ \"h\") --| ($$ \"e\")
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 125
val input = (explode \"hello\")
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 126
in
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 127
(just_e input, just_h input)
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 128
end"
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 129
"((\"e\", [\"l\", \"l\", \"o\"]),(\"h\", [\"l\", \"l\", \"o\"]))"}
38
+ − 130
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 131
The parser @{ML "Scan.optional p x" for p x} returns the result of the parser
58
+ − 132
@{text "p"}, if it succeeds; otherwise it returns
104
+ − 133
the default value @{text "x"}. For example:
38
+ − 134
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 135
@{ML_response [display,gray]
40
+ − 136
"let
+ − 137
val p = Scan.optional ($$ \"h\") \"x\"
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 138
val input1 = (explode \"hello\")
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 139
val input2 = (explode \"world\")
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 140
in
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 141
(p input1, p input2)
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 142
end"
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 143
"((\"h\", [\"e\", \"l\", \"l\", \"o\"]), (\"x\", [\"w\", \"o\", \"r\", \"l\", \"d\"]))"}
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 144
49
+ − 145
The function @{ML Scan.option} works similarly, except no default value can
50
+ − 146
be given. Instead, the result is wrapped as an @{text "option"}-type. For example:
+ − 147
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 148
@{ML_response [display,gray]
50
+ − 149
"let
+ − 150
val p = Scan.option ($$ \"h\")
+ − 151
val input1 = (explode \"hello\")
+ − 152
val input2 = (explode \"world\")
+ − 153
in
+ − 154
(p input1, p input2)
+ − 155
end" "((SOME \"h\", [\"e\", \"l\", \"l\", \"o\"]), (NONE, [\"w\", \"o\", \"r\", \"l\", \"d\"]))"}
49
+ − 156
108
8bea3f74889d
added to the tactical chapter; polished; added the tabularstar environment (which is just tabular*)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 157
The function @{ML "!!"} helps to produce appropriate error messages
220
+ − 158
for parsing. For example if you want to parse @{text p} immediately
58
+ − 159
followed by @{text q}, or start a completely different parser @{text r},
104
+ − 160
you might write:
40
+ − 161
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 162
@{ML [display,gray] "(p -- q) || r" for p q r}
40
+ − 163
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 164
However, this parser is problematic for producing an appropriate error
220
+ − 165
message, if the parsing of @{ML "(p -- q)" for p q} fails. Because in that
+ − 166
case you lose the information that @{text p} should be followed by @{text q}.
+ − 167
To see this assume that @{text p} is present in the input, but it is not
+ − 168
followed by @{text q}. That means @{ML "(p -- q)" for p q} will fail and
+ − 169
hence the alternative parser @{text r} will be tried. However, in many
+ − 170
circumstances this will be the wrong parser for the input ``p-followed-by-something''
+ − 171
and therefore will also fail. The error message is then caused by the failure
+ − 172
of @{text r}, not by the absence of @{text q} in the input. This kind of
+ − 173
situation can be avoided when using the function @{ML "!!"}. This function
+ − 174
aborts the whole process of parsing in case of a failure and prints an error
+ − 175
message. For example if you invoke the parser
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 176
40
+ − 177
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 178
@{ML [display,gray] "(!! (fn _ => \"foo\") ($$ \"h\"))"}
40
+ − 179
58
+ − 180
on @{text [quotes] "hello"}, the parsing succeeds
39
631d12c25bde
substantial changes to the antiquotations (preliminary version)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 181
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 182
@{ML_response [display,gray]
40
+ − 183
"(!! (fn _ => \"foo\") ($$ \"h\")) (explode \"hello\")"
+ − 184
"(\"h\", [\"e\", \"l\", \"l\", \"o\"])"}
+ − 185
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 186
but if you invoke it on @{text [quotes] "world"}
40
+ − 187
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 188
@{ML_response_fake [display,gray] "(!! (fn _ => \"foo\") ($$ \"h\")) (explode \"world\")"
41
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 189
"Exception ABORT raised"}
40
+ − 190
108
8bea3f74889d
added to the tactical chapter; polished; added the tabularstar environment (which is just tabular*)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 191
then the parsing aborts and the error message @{text "foo"} is printed. In order to
120
+ − 192
see the error message properly, you need to prefix the parser with the function
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 193
@{ML "Scan.error"}. For example:
40
+ − 194
74
+ − 195
@{ML_response_fake [display,gray] "Scan.error (!! (fn _ => \"foo\") ($$ \"h\"))"
41
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 196
"Exception Error \"foo\" raised"}
40
+ − 197
219
+ − 198
This ``prefixing'' is usually done by wrappers such as @{ML "OuterSyntax.local_theory"}
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 199
(see Section~\ref{sec:newcommand} which explains this function in more detail).
40
+ − 200
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 201
Let us now return to our example of parsing @{ML "(p -- q) || r" for p q
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 202
r}. If you want to generate the correct error message for p-followed-by-q,
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 203
then you have to write:
38
+ − 204
*}
+ − 205
69
+ − 206
ML{*fun p_followed_by_q p q r =
133
+ − 207
let
+ − 208
val err_msg = (fn _ => p ^ " is not followed by " ^ q)
+ − 209
in
+ − 210
($$ p -- (!! err_msg ($$ q))) || ($$ r -- $$ r)
+ − 211
end *}
38
+ − 212
41
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 213
40
+ − 214
text {*
220
+ − 215
Running this parser with the arguments
+ − 216
@{text [quotes] "h"}, @{text [quotes] "e"} and @{text [quotes] "w"}, and
65
+ − 217
the input @{text [quotes] "holle"}
40
+ − 218
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 219
@{ML_response_fake [display,gray] "Scan.error (p_followed_by_q \"h\" \"e\" \"w\") (explode \"holle\")"
41
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 220
"Exception ERROR \"h is not followed by e\" raised"}
40
+ − 221
65
+ − 222
produces the correct error message. Running it with
40
+ − 223
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 224
@{ML_response [display,gray] "Scan.error (p_followed_by_q \"h\" \"e\" \"w\") (explode \"wworld\")"
40
+ − 225
"((\"w\", \"w\"), [\"o\", \"r\", \"l\", \"d\"])"}
+ − 226
+ − 227
yields the expected parsing.
38
+ − 228
58
+ − 229
The function @{ML "Scan.repeat p" for p} will apply a parser @{text p} as
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 230
often as it succeeds. For example:
40
+ − 231
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 232
@{ML_response [display,gray] "Scan.repeat ($$ \"h\") (explode \"hhhhello\")"
40
+ − 233
"([\"h\", \"h\", \"h\", \"h\"], [\"e\", \"l\", \"l\", \"o\"])"}
+ − 234
+ − 235
Note that @{ML "Scan.repeat"} stores the parsed items in a list. The function
58
+ − 236
@{ML "Scan.repeat1"} is similar, but requires that the parser @{text "p"}
41
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 237
succeeds at least once.
48
+ − 238
58
+ − 239
Also note that the parser would have aborted with the exception @{text MORE}, if
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 240
you had run it only on just @{text [quotes] "hhhh"}. This can be avoided by using
49
+ − 241
the wrapper @{ML Scan.finite} and the ``stopper-token'' @{ML Symbol.stopper}. With
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 242
them you can write:
49
+ − 243
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 244
@{ML_response [display,gray] "Scan.finite Symbol.stopper (Scan.repeat ($$ \"h\")) (explode \"hhhh\")"
49
+ − 245
"([\"h\", \"h\", \"h\", \"h\"], [])"}
+ − 246
65
+ − 247
@{ML Symbol.stopper} is the ``end-of-input'' indicator for parsing strings;
128
+ − 248
other stoppers need to be used when parsing, for example, tokens. However, this kind of
65
+ − 249
manually wrapping is often already done by the surrounding infrastructure.
49
+ − 250
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 251
The function @{ML Scan.repeat} can be used with @{ML Scan.one} to read any
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 252
string as in
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 253
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 254
@{ML_response [display,gray]
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 255
"let
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 256
val p = Scan.repeat (Scan.one Symbol.not_eof)
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 257
val input = (explode \"foo bar foo\")
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 258
in
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 259
Scan.finite Symbol.stopper p input
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 260
end"
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 261
"([\"f\", \"o\", \"o\", \" \", \"b\", \"a\", \"r\", \" \", \"f\", \"o\", \"o\"], [])"}
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 262
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 263
where the function @{ML Symbol.not_eof} ensures that we do not read beyond the
65
+ − 264
end of the input string (i.e.~stopper symbol).
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 265
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 266
The function @{ML "Scan.unless p q" for p q} takes two parsers: if the first one can
60
5b9c6010897b
doem tuning and made the cookbook work again with recent changes (CookBook/Package/Ind_Interface.thy needs to be looked at to see what the problem with the new parser type is)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 267
parse the input, then the whole parser fails; if not, then the second is tried. Therefore
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 268
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 269
@{ML_response_fake_both [display,gray] "Scan.unless ($$ \"h\") ($$ \"w\") (explode \"hello\")"
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 270
"Exception FAIL raised"}
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 271
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 272
fails, while
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 273
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 274
@{ML_response [display,gray] "Scan.unless ($$ \"h\") ($$ \"w\") (explode \"world\")"
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 275
"(\"w\",[\"o\", \"r\", \"l\", \"d\"])"}
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 276
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 277
succeeds.
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 278
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 279
The functions @{ML Scan.repeat} and @{ML Scan.unless} can be combined to read any
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 280
input until a certain marker symbol is reached. In the example below the marker
60
5b9c6010897b
doem tuning and made the cookbook work again with recent changes (CookBook/Package/Ind_Interface.thy needs to be looked at to see what the problem with the new parser type is)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 281
symbol is a @{text [quotes] "*"}.
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 282
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 283
@{ML_response [display,gray]
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 284
"let
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 285
val p = Scan.repeat (Scan.unless ($$ \"*\") (Scan.one Symbol.not_eof))
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 286
val input1 = (explode \"fooooo\")
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 287
val input2 = (explode \"foo*ooo\")
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 288
in
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 289
(Scan.finite Symbol.stopper p input1,
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 290
Scan.finite Symbol.stopper p input2)
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 291
end"
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 292
"(([\"f\", \"o\", \"o\", \"o\", \"o\", \"o\"], []),
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 293
([\"f\", \"o\", \"o\"], [\"*\", \"o\", \"o\", \"o\"]))"}
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 294
220
+ − 295
After parsing is done, you almost always want to apply a function to the parsed
104
+ − 296
items. One way to do this is the function @{ML "(p >> f)" for p f}, which runs
58
+ − 297
first the parser @{text p} and upon successful completion applies the
+ − 298
function @{text f} to the result. For example
38
+ − 299
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 300
@{ML_response [display,gray]
40
+ − 301
"let
193
+ − 302
fun double (x, y) = (x ^ x, y ^ y)
40
+ − 303
in
+ − 304
(($$ \"h\") -- ($$ \"e\") >> double) (explode \"hello\")
+ − 305
end"
+ − 306
"((\"hh\", \"ee\"), [\"l\", \"l\", \"o\"])"}
+ − 307
104
+ − 308
doubles the two parsed input strings; or
59
+ − 309
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 310
@{ML_response [display,gray]
59
+ − 311
"let
104
+ − 312
val p = Scan.repeat (Scan.one Symbol.not_eof)
59
+ − 313
val input = (explode \"foo bar foo\")
+ − 314
in
104
+ − 315
Scan.finite Symbol.stopper (p >> implode) input
59
+ − 316
end"
+ − 317
"(\"foo bar foo\",[])"}
+ − 318
60
5b9c6010897b
doem tuning and made the cookbook work again with recent changes (CookBook/Package/Ind_Interface.thy needs to be looked at to see what the problem with the new parser type is)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 319
where the single-character strings in the parsed output are transformed
59
+ − 320
back into one string.
41
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 321
193
+ − 322
(FIXME: move to an earlier place)
+ − 323
125
+ − 324
The function @{ML Scan.ahead} parses some input, but leaves the original
+ − 325
input unchanged. For example:
+ − 326
+ − 327
@{ML_response [display,gray]
+ − 328
"Scan.ahead (Scan.this_string \"foo\") (explode \"foo\")"
+ − 329
"(\"foo\", [\"f\", \"o\", \"o\"])"}
56
126646f2aa88
added a para on Scan.unless and an exercise about scanning comments
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 330
40
+ − 331
The function @{ML Scan.lift} takes a parser and a pair as arguments. This function applies
+ − 332
the given parser to the second component of the pair and leaves the first component
+ − 333
untouched. For example
38
+ − 334
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 335
@{ML_response [display,gray]
40
+ − 336
"Scan.lift (($$ \"h\") -- ($$ \"e\")) (1,(explode \"hello\"))"
+ − 337
"((\"h\", \"e\"), (1, [\"l\", \"l\", \"o\"]))"}
+ − 338
43
02f76f1b6e7b
added positions to anti-quotations; removed old antiquotation_setup; tuned the text a bit
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 339
(FIXME: In which situations is this useful? Give examples.)
149
+ − 340
+ − 341
\begin{exercise}\label{ex:scancmts}
+ − 342
Write a parser that parses an input string so that any comment enclosed
220
+ − 343
within @{text "(*\<dots>*)"} is replaced by the same comment but enclosed within
149
+ − 344
@{text "(**\<dots>**)"} in the output string. To enclose a string, you can use the
+ − 345
function @{ML "enclose s1 s2 s" for s1 s2 s} which produces the string @{ML
+ − 346
"s1 ^ s ^ s2" for s1 s2 s}.
+ − 347
\end{exercise}
40
+ − 348
*}
+ − 349
41
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 350
section {* Parsing Theory Syntax *}
38
+ − 351
40
+ − 352
text {*
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 353
Most of the time, however, Isabelle developers have to deal with parsing
156
+ − 354
tokens, not strings. These token parsers have the type:
128
+ − 355
*}
+ − 356
+ − 357
ML{*type 'a parser = OuterLex.token list -> 'a * OuterLex.token list*}
+ − 358
+ − 359
text {*
149
+ − 360
The reason for using token parsers is that theory syntax, as well as the
128
+ − 361
parsers for the arguments of proof methods, use the type @{ML_type
+ − 362
OuterLex.token} (which is identical to the type @{ML_type
+ − 363
OuterParse.token}). However, there are also handy parsers for
+ − 364
ML-expressions and ML-files.
42
+ − 365
+ − 366
\begin{readmore}
40
+ − 367
The parser functions for the theory syntax are contained in the structure
42
+ − 368
@{ML_struct OuterParse} defined in the file @{ML_file "Pure/Isar/outer_parse.ML"}.
+ − 369
The definition for tokens is in the file @{ML_file "Pure/Isar/outer_lex.ML"}.
+ − 370
\end{readmore}
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 371
75
+ − 372
The structure @{ML_struct OuterLex} defines several kinds of tokens (for example
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 373
@{ML "Ident" in OuterLex} for identifiers, @{ML "Keyword" in OuterLex} for keywords and
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 374
@{ML "Command" in OuterLex} for commands). Some token parsers take into account the
75
+ − 375
kind of tokens.
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 376
*}
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 377
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 378
text {*
104
+ − 379
The first example shows how to generate a token list out of a string using
128
+ − 380
the function @{ML "OuterSyntax.scan"}. It is given the argument @{ML "Position.none"}
+ − 381
since, at the moment, we are not interested in generating
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 382
precise error messages. The following code
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 383
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 384
@{ML_response_fake [display,gray] "OuterSyntax.scan Position.none \"hello world\""
50
+ − 385
"[Token (\<dots>,(Ident, \"hello\"),\<dots>),
+ − 386
Token (\<dots>,(Space, \" \"),\<dots>),
+ − 387
Token (\<dots>,(Ident, \"world\"),\<dots>)]"}
+ − 388
+ − 389
produces three tokens where the first and the last are identifiers, since
58
+ − 390
@{text [quotes] "hello"} and @{text [quotes] "world"} do not match any
221
+ − 391
other syntactic category.\footnote{Note that because of a possible bug in
+ − 392
the PolyML runtime system, the result is printed as @{text [quotes] "?"}, instead of
75
+ − 393
the tokens.} The second indicates a space.
50
+ − 394
+ − 395
Many parsing functions later on will require spaces, comments and the like
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 396
to have already been filtered out. So from now on we are going to use the
221
+ − 397
functions @{ML filter} and @{ML OuterLex.is_proper} to do this. For example:
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 398
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 399
@{ML_response_fake [display,gray]
50
+ − 400
"let
+ − 401
val input = OuterSyntax.scan Position.none \"hello world\"
+ − 402
in
+ − 403
filter OuterLex.is_proper input
+ − 404
end"
+ − 405
"[Token (\<dots>,(Ident, \"hello\"), \<dots>), Token (\<dots>,(Ident, \"world\"), \<dots>)]"}
+ − 406
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 407
For convenience we define the function:
50
+ − 408
+ − 409
*}
+ − 410
69
+ − 411
ML{*fun filtered_input str =
160
cc9359bfacf4
redefined the functions warning and tracing in order to properly match more antiquotations
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 412
filter OuterLex.is_proper (OuterSyntax.scan Position.none str) *}
50
+ − 413
+ − 414
text {*
+ − 415
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 416
If you now parse
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 417
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 418
@{ML_response_fake [display,gray]
50
+ − 419
"filtered_input \"inductive | for\""
+ − 420
"[Token (\<dots>,(Command, \"inductive\"),\<dots>),
+ − 421
Token (\<dots>,(Keyword, \"|\"),\<dots>),
+ − 422
Token (\<dots>,(Keyword, \"for\"),\<dots>)]"}
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 423
221
+ − 424
you obtain a list consisting of only one command and two keyword tokens.
104
+ − 425
If you want to see which keywords and commands are currently known to Isabelle, type in
75
+ − 426
the following code (you might have to adjust the @{ML print_depth} in order to
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 427
see the complete list):
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 428
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 429
@{ML_response_fake [display,gray]
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 430
"let
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 431
val (keywords, commands) = OuterKeyword.get_lexicons ()
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 432
in
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 433
(Scan.dest_lexicon commands, Scan.dest_lexicon keywords)
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 434
end"
132
+ − 435
"([\"}\", \"{\", \<dots>], [\"\<rightleftharpoons>\", \"\<leftharpoondown>\", \<dots>])"}
42
+ − 436
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 437
The parser @{ML "OuterParse.$$$"} parses a single keyword. For example:
50
+ − 438
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 439
@{ML_response [display,gray]
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 440
"let
50
+ − 441
val input1 = filtered_input \"where for\"
+ − 442
val input2 = filtered_input \"| in\"
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 443
in
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 444
(OuterParse.$$$ \"where\" input1, OuterParse.$$$ \"|\" input2)
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 445
end"
128
+ − 446
"((\"where\",\<dots>), (\"|\",\<dots>))"}
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 447
108
8bea3f74889d
added to the tactical chapter; polished; added the tabularstar environment (which is just tabular*)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 448
Like before, you can sequentially connect parsers with @{ML "--"}. For example:
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 449
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 450
@{ML_response [display,gray]
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 451
"let
50
+ − 452
val input = filtered_input \"| in\"
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 453
in
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 454
(OuterParse.$$$ \"|\" -- OuterParse.$$$ \"in\") input
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 455
end"
183
+ − 456
"((\"|\", \"in\"), [])"}
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 457
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 458
The parser @{ML "OuterParse.enum s p" for s p} parses a possibly empty
58
+ − 459
list of items recognised by the parser @{text p}, where the items being parsed
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 460
are separated by the string @{text s}. For example:
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 461
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 462
@{ML_response [display,gray]
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 463
"let
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 464
val input = filtered_input \"in | in | in foo\"
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 465
in
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 466
(OuterParse.enum \"|\" (OuterParse.$$$ \"in\")) input
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 467
end"
183
+ − 468
"([\"in\", \"in\", \"in\"], [\<dots>])"}
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 469
50
+ − 470
@{ML "OuterParse.enum1"} works similarly, except that the parsed list must
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 471
be non-empty. Note that we had to add a string @{text [quotes] "foo"} at the
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 472
end of the parsed string, otherwise the parser would have consumed all
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 473
tokens and then failed with the exception @{text "MORE"}. Like in the
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 474
previous section, we can avoid this exception using the wrapper @{ML
50
+ − 475
Scan.finite}. This time, however, we have to use the ``stopper-token'' @{ML
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 476
OuterLex.stopper}. We can write:
49
+ − 477
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 478
@{ML_response [display,gray]
49
+ − 479
"let
50
+ − 480
val input = filtered_input \"in | in | in\"
49
+ − 481
in
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 482
Scan.finite OuterLex.stopper
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 483
(OuterParse.enum \"|\" (OuterParse.$$$ \"in\")) input
49
+ − 484
end"
183
+ − 485
"([\"in\", \"in\", \"in\"], [])"}
49
+ − 486
75
+ − 487
The following function will help to run examples.
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 488
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 489
*}
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 490
69
+ − 491
ML{*fun parse p input = Scan.finite OuterLex.stopper (Scan.error p) input *}
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 492
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 493
text {*
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 494
49
+ − 495
The function @{ML "OuterParse.!!!"} can be used to force termination of the
193
+ − 496
parser in case of a dead end, just like @{ML "Scan.!!"} (see previous section).
+ − 497
Except that the error message of @{ML "OuterParse.!!!"} is fixed to be
+ − 498
@{text [quotes] "Outer syntax error"}
221
+ − 499
together with a relatively precise description of the failure. For example:
49
+ − 500
72
7b8c4fe235aa
added an antiquotation option [gray] for gray boxes around displays
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 501
@{ML_response_fake [display,gray]
49
+ − 502
"let
50
+ − 503
val input = filtered_input \"in |\"
49
+ − 504
val parse_bar_then_in = OuterParse.$$$ \"|\" -- OuterParse.$$$ \"in\"
+ − 505
in
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 506
parse (OuterParse.!!! parse_bar_then_in) input
49
+ − 507
end"
+ − 508
"Exception ERROR \"Outer syntax error: keyword \"|\" expected,
+ − 509
but keyword in was found\" raised"
+ − 510
}
42
+ − 511
65
+ − 512
\begin{exercise} (FIXME)
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 513
A type-identifier, for example @{typ "'a"}, is a token of
54
+ − 514
kind @{ML "Keyword" in OuterLex}. It can be parsed using
+ − 515
the function @{ML OuterParse.type_ident}.
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 516
\end{exercise}
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 517
104
+ − 518
(FIXME: or give parser for numbers)
53
0c3580c831a4
removed the @{ML ...} antiquotation in favour of @{ML_open ...x}
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 519
125
+ − 520
Whenever there is a possibility that the processing of user input can fail,
221
+ − 521
it is a good idea to give all available information about where the error
220
+ − 522
occurred. For this Isabelle can attach positional information to tokens
125
+ − 523
and then thread this information up the processing chain. To see this,
128
+ − 524
modify the function @{ML filtered_input} described earlier to
41
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 525
*}
b11653b11bd3
further progress on the parsing section and tuning on the antiqu's
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 526
125
+ − 527
ML{*fun filtered_input' str =
+ − 528
filter OuterLex.is_proper (OuterSyntax.scan (Position.line 7) str) *}
49
+ − 529
+ − 530
text {*
125
+ − 531
where we pretend the parsed string starts on line 7. An example is
49
+ − 532
125
+ − 533
@{ML_response_fake [display,gray]
+ − 534
"filtered_input' \"foo \\n bar\""
+ − 535
"[Token ((\"foo\", ({line=7, end_line=7}, {line=7})), (Ident, \"foo\"), \<dots>),
+ − 536
Token ((\"bar\", ({line=8, end_line=8}, {line=8})), (Ident, \"bar\"), \<dots>)]"}
+ − 537
+ − 538
in which the @{text [quotes] "\\n"} causes the second token to be in
+ − 539
line 8.
+ − 540
126
+ − 541
By using the parser @{ML OuterParse.position} you can decode the positional
125
+ − 542
information and return it as part of the parsed input. For example
+ − 543
+ − 544
@{ML_response_fake [display,gray]
+ − 545
"let
+ − 546
val input = (filtered_input' \"where\")
+ − 547
in
+ − 548
parse (OuterParse.position (OuterParse.$$$ \"where\")) input
+ − 549
end"
+ − 550
"((\"where\", {line=7, end_line=7}), [])"}
+ − 551
+ − 552
\begin{readmore}
+ − 553
The functions related to positions are implemented in the file
+ − 554
@{ML_file "Pure/General/position.ML"}.
+ − 555
\end{readmore}
49
+ − 556
+ − 557
*}
+ − 558
193
+ − 559
section {* Context Parser (TBD) *}
+ − 560
+ − 561
text {*
+ − 562
Used for example in \isacommand{attribute\_setup} and \isacommand{method\_setup}.
+ − 563
*}
+ − 564
207
+ − 565
section {* Argument and Attribute Parsers (TBD) *}
+ − 566
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 567
section {* Parsing Inner Syntax *}
42
+ − 568
125
+ − 569
text {*
+ − 570
There is usually no need to write your own parser for parsing inner syntax, that is
+ − 571
for terms and types: you can just call the pre-defined parsers. Terms can
+ − 572
be parsed using the function @{ML OuterParse.term}. For example:
+ − 573
+ − 574
@{ML_response [display,gray]
+ − 575
"let
+ − 576
val input = OuterSyntax.scan Position.none \"foo\"
44
dee4b3e66dfe
added a readme chapter for prospective authors; added commands for referring to the Isar Reference Manual
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 577
in
125
+ − 578
OuterParse.term input
+ − 579
end"
+ − 580
"(\"\\^E\\^Ftoken\\^Efoo\\^E\\^F\\^E\", [])"}
+ − 581
+ − 582
The function @{ML OuterParse.prop} is similar, except that it gives a different
127
+ − 583
error message, when parsing fails. As you can see, the parser not just returns
+ − 584
the parsed string, but also some encoded information. You can decode the
+ − 585
information with the function @{ML YXML.parse}. For example
+ − 586
+ − 587
@{ML_response [display,gray]
+ − 588
"YXML.parse \"\\^E\\^Ftoken\\^Efoo\\^E\\^F\\^E\""
+ − 589
"XML.Elem (\"token\", [], [XML.Text \"foo\"])"}
+ − 590
149
+ − 591
The result of the decoding is an XML-tree. You can see better what is going on if
131
+ − 592
you replace @{ML Position.none} by @{ML "Position.line 42"}, say:
101
+ − 593
125
+ − 594
@{ML_response [display,gray]
+ − 595
"let
+ − 596
val input = OuterSyntax.scan (Position.line 42) \"foo\"
+ − 597
in
127
+ − 598
YXML.parse (fst (OuterParse.term input))
125
+ − 599
end"
127
+ − 600
"XML.Elem (\"token\", [(\"line\", \"42\"), (\"end_line\", \"42\")], [XML.Text \"foo\"])"}
125
+ − 601
149
+ − 602
The positional information is stored as part of an XML-tree so that code
+ − 603
called later on will be able to give more precise error messages.
125
+ − 604
127
+ − 605
\begin{readmore}
128
+ − 606
The functions to do with input and output of XML and YXML are defined
127
+ − 607
in @{ML_file "Pure/General/xml.ML"} and @{ML_file "Pure/General/yxml.ML"}.
+ − 608
\end{readmore}
160
cc9359bfacf4
redefined the functions warning and tracing in order to properly match more antiquotations
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 609
125
+ − 610
*}
101
+ − 611
116
+ − 612
section {* Parsing Specifications\label{sec:parsingspecs} *}
101
+ − 613
+ − 614
text {*
121
+ − 615
There are a number of special purpose parsers that help with parsing
156
+ − 616
specifications of function definitions, inductive predicates and so on. In
220
+ − 617
Chapter~\ref{chp:package}, for example, we will need to parse specifications
121
+ − 618
for inductive predicates of the form:
+ − 619
*}
101
+ − 620
219
+ − 621
(*
121
+ − 622
simple_inductive
+ − 623
even and odd
+ − 624
where
+ − 625
even0: "even 0"
+ − 626
| evenS: "odd n \<Longrightarrow> even (Suc n)"
+ − 627
| oddS: "even n \<Longrightarrow> odd (Suc n)"
219
+ − 628
*)
101
+ − 629
+ − 630
text {*
121
+ − 631
For this we are going to use the parser:
101
+ − 632
*}
+ − 633
121
+ − 634
ML %linenosgray{*val spec_parser =
126
+ − 635
OuterParse.fixes --
+ − 636
Scan.optional
+ − 637
(OuterParse.$$$ "where" |--
+ − 638
OuterParse.!!!
+ − 639
(OuterParse.enum1 "|"
+ − 640
(SpecParse.opt_thm_name ":" -- OuterParse.prop))) []*}
120
+ − 641
101
+ − 642
text {*
126
+ − 643
Note that the parser does not parse the keyword \simpleinductive, even if it is
+ − 644
meant to process definitions as shown above. The parser of the keyword
128
+ − 645
will be given by the infrastructure that will eventually call @{ML spec_parser}.
126
+ − 646
+ − 647
124
+ − 648
To see what the parser returns, let us parse the string corresponding to the
121
+ − 649
definition of @{term even} and @{term odd}:
+ − 650
101
+ − 651
@{ML_response [display,gray]
+ − 652
"let
+ − 653
val input = filtered_input
+ − 654
(\"even and odd \" ^
+ − 655
\"where \" ^
+ − 656
\" even0[intro]: \\\"even 0\\\" \" ^
+ − 657
\"| evenS[intro]: \\\"odd n \<Longrightarrow> even (Suc n)\\\" \" ^
+ − 658
\"| oddS[intro]: \\\"even n \<Longrightarrow> odd (Suc n)\\\"\")
+ − 659
in
120
+ − 660
parse spec_parser input
101
+ − 661
end"
186
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 662
"(([(even, NONE, NoSyn), (odd, NONE, NoSyn)],
101
+ − 663
[((even0,\<dots>), \"\\^E\\^Ftoken\\^Eeven 0\\^E\\^F\\^E\"),
+ − 664
((evenS,\<dots>), \"\\^E\\^Ftoken\\^Eodd n \<Longrightarrow> even (Suc n)\\^E\\^F\\^E\"),
+ − 665
((oddS,\<dots>), \"\\^E\\^Ftoken\\^Eeven n \<Longrightarrow> odd (Suc n)\\^E\\^F\\^E\")]), [])"}
121
+ − 666
186
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 667
As you see, the result is a pair consisting of a list of
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 668
variables with optional type-annotation and syntax-annotation, and a list of
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 669
rules where every rule has optionally a name and an attribute.
121
+ − 670
186
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 671
The function @{ML OuterParse.fixes} in Line 2 of the parser reads an
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 672
\isacommand{and}-separated
124
+ − 673
list of variables that can include optional type annotations and syntax translations.
121
+ − 674
For example:\footnote{Note that in the code we need to write
+ − 675
@{text "\\\"int \<Rightarrow> bool\\\""} in order to properly escape the double quotes
+ − 676
in the compound type.}
+ − 677
+ − 678
@{ML_response [display,gray]
+ − 679
"let
+ − 680
val input = filtered_input
+ − 681
\"foo::\\\"int \<Rightarrow> bool\\\" and bar::nat (\\\"BAR\\\" 100) and blonk\"
+ − 682
in
219
+ − 683
parse OuterParse.fixes input
121
+ − 684
end"
+ − 685
"([(foo, SOME \"\\^E\\^Ftoken\\^Eint \<Rightarrow> bool\\^E\\^F\\^E\", NoSyn),
+ − 686
(bar, SOME \"\\^E\\^Ftoken\\^Enat\\^E\\^F\\^E\", Mixfix (\"BAR\", [], 100)),
+ − 687
(blonk, NONE, NoSyn)],[])"}
50
+ − 688
*}
+ − 689
121
+ − 690
text {*
156
+ − 691
Whenever types are given, they are stored in the @{ML SOME}s. The types are
+ − 692
not yet used to type the variables: this must be done by type-inference later
149
+ − 693
on. Since types are part of the inner syntax they are strings with some
+ − 694
encoded information (see previous section). If a syntax translation is
220
+ − 695
present for a variable, then it is stored in the @{ML Mixfix} data structure;
149
+ − 696
no syntax translation is indicated by @{ML NoSyn}.
121
+ − 697
+ − 698
\begin{readmore}
220
+ − 699
The data structure for syntax annotations is defined in @{ML_file "Pure/Syntax/mixfix.ML"}.
121
+ − 700
\end{readmore}
+ − 701
186
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 702
Lines 3 to 7 in the function @{ML spec_parser} implement the parser for a
219
+ − 703
list of introduction rules, that is propositions with theorem annotations
+ − 704
such as rule names and attributes. The introduction rules are propositions
+ − 705
parsed by @{ML OuterParse.prop}. However, they can include an optional
+ − 706
theorem name plus some attributes. For example
121
+ − 707
+ − 708
@{ML_response [display,gray] "let
+ − 709
val input = filtered_input \"foo_lemma[intro,dest!]:\"
+ − 710
val ((name, attrib), _) = parse (SpecParse.thm_name \":\") input
+ − 711
in
+ − 712
(name, map Args.dest_src attrib)
+ − 713
end" "(foo_lemma, [((\"intro\", []), \<dots>), ((\"dest\", [\<dots>]), \<dots>)])"}
+ − 714
+ − 715
The function @{ML opt_thm_name in SpecParse} is the ``optional'' variant of
131
+ − 716
@{ML thm_name in SpecParse}. Theorem names can contain attributes. The name
+ − 717
has to end with @{text [quotes] ":"}---see the argument of
186
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 718
the function @{ML SpecParse.opt_thm_name} in Line 7.
121
+ − 719
+ − 720
\begin{readmore}
+ − 721
Attributes and arguments are implemented in the files @{ML_file "Pure/Isar/attrib.ML"}
+ − 722
and @{ML_file "Pure/Isar/args.ML"}.
+ − 723
\end{readmore}
101
+ − 724
*}
65
+ − 725
193
+ − 726
text_raw {*
+ − 727
\begin{exercise}
207
+ − 728
Have a look at how the parser @{ML SpecParse.where_alt_specs} is implemented
+ − 729
in file @{ML_file "Pure/Isar/spec_parse.ML"}. This parser corresponds
+ − 730
to the ``where-part'' of the introduction rules given above. Below
+ − 731
we paraphrase the code of @{ML SpecParse.where_alt_specs} adapted to our
+ − 732
purposes.
193
+ − 733
\begin{isabelle}
+ − 734
*}
+ − 735
ML %linenosgray{*val spec_parser' =
+ − 736
OuterParse.fixes --
+ − 737
Scan.optional
+ − 738
(OuterParse.$$$ "where" |--
+ − 739
OuterParse.!!!
+ − 740
(OuterParse.enum1 "|"
+ − 741
((SpecParse.opt_thm_name ":" -- OuterParse.prop) --|
+ − 742
Scan.option (Scan.ahead (OuterParse.name ||
+ − 743
OuterParse.$$$ "[") --
+ − 744
OuterParse.!!! (OuterParse.$$$ "|"))))) [] *}
+ − 745
text_raw {*
+ − 746
\end{isabelle}
207
+ − 747
Both parsers accept the same input, but if you look closely, you can notice
+ − 748
an additional ``tail'' (Lines 8 to 10) in @{ML spec_parser'}. What is the purpose of
+ − 749
this additional ``tail''?
193
+ − 750
\end{exercise}
+ − 751
*}
+ − 752
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 753
section {* New Commands and Keyword Files\label{sec:newcommand} *}
65
+ − 754
+ − 755
text {*
68
+ − 756
Often new commands, for example for providing new definitional principles,
+ − 757
need to be implemented. While this is not difficult on the ML-level,
66
+ − 758
new commands, in order to be useful, need to be recognised by
65
+ − 759
ProofGeneral. This results in some subtle configuration issues, which we
+ − 760
will explain in this section.
+ − 761
74
+ − 762
To keep things simple, let us start with a ``silly'' command that does nothing
+ − 763
at all. We shall name this command \isacommand{foobar}. On the ML-level it can be
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 764
defined as:
68
+ − 765
*}
65
+ − 766
69
+ − 767
ML{*let
219
+ − 768
val do_nothing = Scan.succeed (LocalTheory.theory I)
68
+ − 769
val kind = OuterKeyword.thy_decl
65
+ − 770
in
219
+ − 771
OuterSyntax.local_theory "foobar" "description of foobar" kind do_nothing
69
+ − 772
end *}
65
+ − 773
68
+ − 774
text {*
219
+ − 775
The crucial function @{ML OuterSyntax.local_theory} expects a name for the command, a
+ − 776
short description, a kind indicator (which we will explain later more thoroughly) and a
+ − 777
parser producing a local theory transition (its purpose will also explained
66
+ − 778
later).
65
+ − 779
101
+ − 780
While this is everything you have to do on the ML-level, you need a keyword
68
+ − 781
file that can be loaded by ProofGeneral. This is to enable ProofGeneral to
+ − 782
recognise \isacommand{foobar} as a command. Such a keyword file can be
74
+ − 783
generated with the command-line:
68
+ − 784
74
+ − 785
@{text [display] "$ isabelle keywords -k foobar some_log_files"}
65
+ − 786
74
+ − 787
The option @{text "-k foobar"} indicates which postfix the name of the keyword file
80
+ − 788
will be assigned. In the case above the file will be named @{text
86
+ − 789
"isar-keywords-foobar.el"}. This command requires log files to be
68
+ − 790
present (in order to extract the keywords from them). To generate these log
101
+ − 791
files, you first need to package the code above into a separate theory file named
68
+ − 792
@{text "Command.thy"}, say---see Figure~\ref{fig:commandtheory} for the
+ − 793
complete code.
65
+ − 794
66
+ − 795
+ − 796
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+ − 797
\begin{figure}[t]
69
+ − 798
\begin{graybox}\small
66
+ − 799
\isacommand{theory}~@{text Command}\\
+ − 800
\isacommand{imports}~@{text Main}\\
+ − 801
\isacommand{begin}\\
85
+ − 802
\isacommand{ML}~@{text "\<verbopen>"}\\
66
+ − 803
@{ML
+ − 804
"let
219
+ − 805
val do_nothing = Scan.succeed (LocalTheory.theory I)
68
+ − 806
val kind = OuterKeyword.thy_decl
66
+ − 807
in
219
+ − 808
OuterSyntax.local_theory \"foobar\" \"description of foobar\" kind do_nothing
66
+ − 809
end"}\\
85
+ − 810
@{text "\<verbclose>"}\\
66
+ − 811
\isacommand{end}
80
+ − 812
\end{graybox}
219
+ − 813
\caption{The file @{text "Command.thy"} is necessary for generating a log
66
+ − 814
file. This log file enables Isabelle to generate a keyword file containing
68
+ − 815
the command \isacommand{foobar}.\label{fig:commandtheory}}
66
+ − 816
\end{figure}
+ − 817
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+ − 818
75
+ − 819
For our purposes it is sufficient to use the log files of the theories
68
+ − 820
@{text "Pure"}, @{text "HOL"} and @{text "Pure-ProofGeneral"}, as well as
75
+ − 821
the log file for the theory @{text "Command.thy"}, which contains the new
+ − 822
\isacommand{foobar}-command. If you target other logics besides HOL, such
74
+ − 823
as Nominal or ZF, then you need to adapt the log files appropriately.
104
+ − 824
74
+ − 825
@{text Pure} and @{text HOL} are usually compiled during the installation of
+ − 826
Isabelle. So log files for them should be already available. If not, then
75
+ − 827
they can be conveniently compiled with the help of the build-script from the Isabelle
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 828
distribution.
65
+ − 829
+ − 830
@{text [display]
+ − 831
"$ ./build -m \"Pure\"
+ − 832
$ ./build -m \"HOL\""}
+ − 833
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 834
The @{text "Pure-ProofGeneral"} theory needs to be compiled with:
65
+ − 835
+ − 836
@{text [display] "$ ./build -m \"Pure-ProofGeneral\" \"Pure\""}
+ − 837
101
+ − 838
For the theory @{text "Command.thy"}, you first need to create a ``managed'' subdirectory
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 839
with:
66
+ − 840
68
+ − 841
@{text [display] "$ isabelle mkdir FoobarCommand"}
66
+ − 842
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 843
This generates a directory containing the files:
66
+ − 844
+ − 845
@{text [display]
+ − 846
"./IsaMakefile
68
+ − 847
./FoobarCommand/ROOT.ML
+ − 848
./FoobarCommand/document
+ − 849
./FoobarCommand/document/root.tex"}
65
+ − 850
+ − 851
101
+ − 852
You need to copy the file @{text "Command.thy"} into the directory @{text "FoobarCommand"}
66
+ − 853
and add the line
+ − 854
207
+ − 855
@{text [display] "no_document use_thy \"Command\";"}
66
+ − 856
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 857
to the file @{text "./FoobarCommand/ROOT.ML"}. You can now compile the theory by just typing:
65
+ − 858
+ − 859
@{text [display] "$ isabelle make"}
+ − 860
101
+ − 861
If the compilation succeeds, you have finally created all the necessary log files.
+ − 862
They are stored in the directory
65
+ − 863
66
+ − 864
@{text [display] "~/.isabelle/heaps/Isabelle2008/polyml-5.2.1_x86-linux/log"}
65
+ − 865
74
+ − 866
or something similar depending on your Isabelle distribution and architecture.
+ − 867
One quick way to assign a shell variable to this directory is by typing
66
+ − 868
+ − 869
@{text [display] "$ ISABELLE_LOGS=\"$(isabelle getenv -b ISABELLE_OUTPUT)\"/log"}
+ − 870
156
+ − 871
on the Unix prompt. If you now type @{text "ls $ISABELLE_LOGS"}, then the
128
+ − 872
directory should include the files:
65
+ − 873
+ − 874
@{text [display]
+ − 875
"Pure.gz
+ − 876
HOL.gz
+ − 877
Pure-ProofGeneral.gz
68
+ − 878
HOL-FoobarCommand.gz"}
65
+ − 879
101
+ − 880
From them you can create the keyword files. Assuming the name
75
+ − 881
of the directory is in @{text "$ISABELLE_LOGS"},
74
+ − 882
then the Unix command for creating the keyword file is:
65
+ − 883
+ − 884
@{text [display]
68
+ − 885
"$ isabelle keywords -k foobar
80
+ − 886
$ISABELLE_LOGS/{Pure.gz,HOL.gz,Pure-ProofGeneral.gz,HOL-FoobarCommand.gz}"}
65
+ − 887
80
+ − 888
The result is the file @{text "isar-keywords-foobar.el"}. It should contain
86
+ − 889
the string @{text "foobar"} twice.\footnote{To see whether things are fine, check
80
+ − 890
that @{text "grep foobar"} on this file returns something
86
+ − 891
non-empty.} This keyword file needs to
80
+ − 892
be copied into the directory @{text "~/.isabelle/etc"}. To make Isabelle
101
+ − 893
aware of this keyword file, you have to start Isabelle with the option @{text
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 894
"-k foobar"}, that is:
65
+ − 895
80
+ − 896
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 897
@{text [display] "$ isabelle emacs -k foobar a_theory_file"}
65
+ − 898
101
+ − 899
If you now build a theory on top of @{text "Command.thy"},
+ − 900
then the command \isacommand{foobar} can be used.
74
+ − 901
Similarly with any other new command.
65
+ − 902
+ − 903
75
+ − 904
At the moment \isacommand{foobar} is not very useful. Let us refine it a bit
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 905
next by letting it take a proposition as argument and printing this proposition
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 906
inside the tracing buffer.
68
+ − 907
75
+ − 908
The crucial part of a command is the function that determines the behaviour
+ − 909
of the command. In the code above we used a ``do-nothing''-function, which
+ − 910
because of @{ML Scan.succeed} does not parse any argument, but immediately
219
+ − 911
returns the simple function @{ML "LocalTheory.theory I"}. We can
75
+ − 912
replace this code by a function that first parses a proposition (using the
+ − 913
parser @{ML OuterParse.prop}), then prints out the tracing
219
+ − 914
information (using a new function @{text trace_prop}) and
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 915
finally does nothing. For this you can write:
68
+ − 916
*}
+ − 917
69
+ − 918
ML{*let
219
+ − 919
fun trace_prop str =
218
7ff7325e3b4e
started to adapt the rest of chapter 5 to the simplified version without parameters (they will be described in the extension section)
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 920
LocalTheory.theory (fn lthy => (tracing str; lthy))
75
+ − 921
219
+ − 922
val trace_prop_parser = OuterParse.prop >> trace_prop
68
+ − 923
val kind = OuterKeyword.thy_decl
+ − 924
in
219
+ − 925
OuterSyntax.local_theory "foobar" "traces a proposition"
+ − 926
kind trace_prop_parser
69
+ − 927
end *}
68
+ − 928
+ − 929
text {*
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 930
Now you can type
68
+ − 931
74
+ − 932
\begin{isabelle}
+ − 933
\isacommand{foobar}~@{text [quotes] "True \<and> False"}\\
75
+ − 934
@{text "> \"True \<and> False\""}
74
+ − 935
\end{isabelle}
68
+ − 936
+ − 937
and see the proposition in the tracing buffer.
+ − 938
219
+ − 939
Note that so far we used @{ML thy_decl in OuterKeyword} as the kind
+ − 940
indicator for the command. This means that the command finishes as soon as
+ − 941
the arguments are processed. Examples of this kind of commands are
+ − 942
\isacommand{definition} and \isacommand{declare}. In other cases, commands
+ − 943
are expected to parse some arguments, for example a proposition, and then
+ − 944
``open up'' a proof in order to prove the proposition (for example
86
+ − 945
\isacommand{lemma}) or prove some other properties (for example
219
+ − 946
\isacommand{function}). To achieve this kind of behaviour, you have to use
+ − 947
the kind indicator @{ML thy_goal in OuterKeyword} and the function @{ML
+ − 948
"local_theory_to_proof" in OuterSyntax} to set up the command. Note,
+ − 949
however, once you change the ``kind'' of a command from @{ML thy_decl in
+ − 950
OuterKeyword} to @{ML thy_goal in OuterKeyword} then the keyword file needs
+ − 951
to be re-created!
68
+ − 952
75
+ − 953
Below we change \isacommand{foobar} so that it takes a proposition as
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 954
argument and then starts a proof in order to prove it. Therefore in Line 13,
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 955
we set the kind indicator to @{ML thy_goal in OuterKeyword}.
68
+ − 956
*}
+ − 957
114
+ − 958
ML%linenosgray{*let
219
+ − 959
fun prove_prop str ctxt =
68
+ − 960
let
+ − 961
val prop = Syntax.read_prop ctxt str
+ − 962
in
75
+ − 963
Proof.theorem_i NONE (K I) [[(prop,[])]] ctxt
68
+ − 964
end;
+ − 965
219
+ − 966
val prove_prop_parser = OuterParse.prop >> prove_prop
68
+ − 967
val kind = OuterKeyword.thy_goal
+ − 968
in
219
+ − 969
OuterSyntax.local_theory_to_proof "foobar" "proving a proposition"
+ − 970
kind prove_prop_parser
69
+ − 971
end *}
68
+ − 972
+ − 973
text {*
219
+ − 974
The function @{text prove_prop} in Lines 2 to 7 takes a string (the proposition to be
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 975
proved) and a context as argument. The context is necessary in order to be able to use
74
+ − 976
@{ML Syntax.read_prop}, which converts a string into a proper proposition.
75
+ − 977
In Line 6 the function @{ML Proof.theorem_i} starts the proof for the
+ − 978
proposition. Its argument @{ML NONE} stands for a locale (which we chose to
+ − 979
omit); the argument @{ML "(K I)"} stands for a function that determines what
+ − 980
should be done with the theorem once it is proved (we chose to just forget
219
+ − 981
about it). Line 9 contains the parser for the proposition.
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 982
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 983
If you now type \isacommand{foobar}~@{text [quotes] "True \<and> True"}, you obtain the following
219
+ − 984
proof state
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 985
74
+ − 986
\begin{isabelle}
80
+ − 987
\isacommand{foobar}~@{text [quotes] "True \<and> True"}\\
102
5e309df58557
general cleaning up; deleted antiquotation ML_text; adjusted pathnames of various files in the distribution
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 988
@{text "goal (1 subgoal):"}\\
74
+ − 989
@{text "1. True \<and> True"}
+ − 990
\end{isabelle}
68
+ − 991
219
+ − 992
and you can build the following proof
68
+ − 993
74
+ − 994
\begin{isabelle}
80
+ − 995
\isacommand{foobar}~@{text [quotes] "True \<and> True"}\\
74
+ − 996
\isacommand{apply}@{text "(rule conjI)"}\\
+ − 997
\isacommand{apply}@{text "(rule TrueI)+"}\\
+ − 998
\isacommand{done}
+ − 999
\end{isabelle}
+ − 1000
75
+ − 1001
(FIXME read a name and show how to store theorems)
65
+ − 1002
*}
+ − 1003
211
d5accbc67e1b
more work on simple inductive and marked all sections that are still seriously incomplete with TBD
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1004
section {* Methods (TBD) *}
178
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1005
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1006
text {*
207
+ − 1007
(FIXME: maybe move to after the tactic section)
+ − 1008
221
+ − 1009
Methods are central to Isabelle. They are the ones you use for example
186
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1010
in \isacommand{apply}. To print out all currently known methods you can use the
192
+ − 1011
Isabelle command:
178
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1012
207
+ − 1013
\begin{isabelle}
+ − 1014
\isacommand{print\_methods}\\
+ − 1015
@{text "> methods:"}\\
+ − 1016
@{text "> -: do nothing (insert current facts only)"}\\
+ − 1017
@{text "> HOL.default: apply some intro/elim rule (potentially classical)"}\\
+ − 1018
@{text "> ..."}
+ − 1019
\end{isabelle}
178
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1020
193
+ − 1021
An example of a very simple method is:
178
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1022
*}
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1023
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1024
method_setup %gray foobar_meth =
181
+ − 1025
{* Scan.succeed
+ − 1026
(K (SIMPLE_METHOD ((etac @{thm conjE} THEN' rtac @{thm conjI}) 1))) *}
207
+ − 1027
"foobar method for conjE and conjI"
178
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1028
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1029
text {*
186
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1030
It defines the method @{text foobar_meth}, which takes no arguments (therefore the
207
+ − 1031
parser @{ML Scan.succeed}) and only applies a single tactic, namely the tactic which
+ − 1032
applies @{thm [source] conjE} and then @{thm [source] conjI}. The function @{ML SIMPLE_METHOD}
+ − 1033
turns such a tactic into a method. @{text "Foobar_meth"} can be used as follows
178
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1034
*}
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1035
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1036
lemma shows "A \<and> B \<Longrightarrow> C \<and> D"
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1037
apply(foobar_meth)
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1038
txt {*
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1039
where it results in the goal state
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1040
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1041
\begin{minipage}{\textwidth}
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1042
@{subgoals}
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1043
\end{minipage} *}
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1044
(*<*)oops(*>*)
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1045
193
+ − 1046
+ − 1047
(*
+ − 1048
ML {* SIMPLE_METHOD *}
+ − 1049
ML {* METHOD *}
+ − 1050
ML {* K (SIMPLE_METHOD ((etac @{thm conjE} THEN' rtac @{thm conjI}) 1)) *}
+ − 1051
ML {* Scan.succeed *}
+ − 1052
*)
+ − 1053
186
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1054
text {*
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1055
(FIXME: explain a version of rule-tac)
371e4375c994
made the Ackermann function example safer and included suggestions from MW
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1056
*}
178
fb8f22dd8ad0
adapted to latest Attrib.setup changes and more work on the simple induct chapter
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1057
75
+ − 1058
(*<*)
194
+ − 1059
(* THIS IS AN OLD VERSION OF THE PARSING CHAPTER BY JEREMY DAWSON *)
38
+ − 1060
chapter {* Parsing *}
+ − 1061
+ − 1062
text {*
+ − 1063
4
+ − 1064
Lots of Standard ML code is given in this document, for various reasons,
+ − 1065
including:
+ − 1066
\begin{itemize}
+ − 1067
\item direct quotation of code found in the Isabelle source files,
+ − 1068
or simplified versions of such code
+ − 1069
\item identifiers found in the Isabelle source code, with their types
+ − 1070
(or specialisations of their types)
+ − 1071
\item code examples, which can be run by the reader, to help illustrate the
+ − 1072
behaviour of functions found in the Isabelle source code
+ − 1073
\item ancillary functions, not from the Isabelle source code,
+ − 1074
which enable the reader to run relevant code examples
+ − 1075
\item type abbreviations, which help explain the uses of certain functions
+ − 1076
\end{itemize}
+ − 1077
+ − 1078
*}
+ − 1079
+ − 1080
section {* Parsing Isar input *}
+ − 1081
+ − 1082
text {*
+ − 1083
+ − 1084
The typical parsing function has the type
+ − 1085
\texttt{'src -> 'res * 'src}, with input
+ − 1086
of type \texttt{'src}, returning a result
+ − 1087
of type \texttt{'res}, which is (or is derived from) the first part of the
+ − 1088
input, and also returning the remainder of the input.
+ − 1089
(In the common case, when it is clear what the ``remainder of the input''
+ − 1090
means, we will just say that the functions ``returns'' the
+ − 1091
value of type \texttt{'res}).
+ − 1092
An exception is raised if an appropriate value
+ − 1093
cannot be produced from the input.
+ − 1094
A range of exceptions can be used to identify different reasons
+ − 1095
for the failure of a parse.
+ − 1096
+ − 1097
This contrasts the standard parsing function in Standard ML,
+ − 1098
which is of type
+ − 1099
\texttt{type ('res, 'src) reader = 'src -> ('res * 'src) option};
+ − 1100
(for example, \texttt{List.getItem} and \texttt{Substring.getc}).
+ − 1101
However, much of the discussion at
+ − 1102
FIX file:/home/jeremy/html/ml/SMLBasis/string-cvt.html
+ − 1103
is relevant.
+ − 1104
+ − 1105
Naturally one may convert between the two different sorts of parsing functions
+ − 1106
as follows:
+ − 1107
\begin{verbatim}
+ − 1108
open StringCvt ;
+ − 1109
type ('res, 'src) ex_reader = 'src -> 'res * 'src
75
+ − 1110
ex_reader : ('res, 'src) reader -> ('res, 'src) ex_reader
4
+ − 1111
fun ex_reader rdr src = Option.valOf (rdr src) ;
75
+ − 1112
reader : ('res, 'src) ex_reader -> ('res, 'src) reader
4
+ − 1113
fun reader exrdr src = SOME (exrdr src) handle _ => NONE ;
+ − 1114
\end{verbatim}
+ − 1115
+ − 1116
*}
+ − 1117
+ − 1118
section{* The \texttt{Scan} structure *}
+ − 1119
+ − 1120
text {*
+ − 1121
The source file is \texttt{src/General/scan.ML}.
+ − 1122
This structure provides functions for using and combining parsing functions
+ − 1123
of the type \texttt{'src -> 'res * 'src}.
+ − 1124
Three exceptions are used:
+ − 1125
\begin{verbatim}
+ − 1126
exception MORE of string option; (*need more input (prompt)*)
+ − 1127
exception FAIL of string option; (*try alternatives (reason of failure)*)
+ − 1128
exception ABORT of string; (*dead end*)
+ − 1129
\end{verbatim}
+ − 1130
Many functions in this structure (generally those with names composed of
+ − 1131
symbols) are declared as infix.
+ − 1132
+ − 1133
Some functions from that structure are
+ − 1134
\begin{verbatim}
+ − 1135
|-- : ('src -> 'res1 * 'src') * ('src' -> 'res2 * 'src'') ->
+ − 1136
'src -> 'res2 * 'src''
+ − 1137
--| : ('src -> 'res1 * 'src') * ('src' -> 'res2 * 'src'') ->
+ − 1138
'src -> 'res1 * 'src''
+ − 1139
-- : ('src -> 'res1 * 'src') * ('src' -> 'res2 * 'src'') ->
+ − 1140
'src -> ('res1 * 'res2) * 'src''
+ − 1141
^^ : ('src -> string * 'src') * ('src' -> string * 'src'') ->
+ − 1142
'src -> string * 'src''
+ − 1143
\end{verbatim}
+ − 1144
These functions parse a result off the input source twice.
+ − 1145
+ − 1146
\texttt{|--} and \texttt{--|}
+ − 1147
return the first result and the second result, respectively.
+ − 1148
+ − 1149
\texttt{--} returns both.
+ − 1150
+ − 1151
\verb|^^| returns the result of concatenating the two results
+ − 1152
(which must be strings).
+ − 1153
+ − 1154
Note how, although the types
+ − 1155
\texttt{'src}, \texttt{'src'} and \texttt{'src''} will normally be the same,
+ − 1156
the types as shown help suggest the behaviour of the functions.
+ − 1157
\begin{verbatim}
+ − 1158
:-- : ('src -> 'res1 * 'src') * ('res1 -> 'src' -> 'res2 * 'src'') ->
+ − 1159
'src -> ('res1 * 'res2) * 'src''
+ − 1160
:|-- : ('src -> 'res1 * 'src') * ('res1 -> 'src' -> 'res2 * 'src'') ->
+ − 1161
'src -> 'res2 * 'src''
+ − 1162
\end{verbatim}
+ − 1163
These are similar to \texttt{|--} and \texttt{--|},
+ − 1164
except that the second parsing function can depend on the result of the first.
+ − 1165
\begin{verbatim}
+ − 1166
>> : ('src -> 'res1 * 'src') * ('res1 -> 'res2) -> 'src -> 'res2 * 'src'
+ − 1167
|| : ('src -> 'res_src) * ('src -> 'res_src) -> 'src -> 'res_src
+ − 1168
\end{verbatim}
+ − 1169
\texttt{p >> f} applies a function \texttt{f} to the result of a parse.
+ − 1170
+ − 1171
\texttt{||} tries a second parsing function if the first one
+ − 1172
fails by raising an exception of the form \texttt{FAIL \_}.
+ − 1173
+ − 1174
\begin{verbatim}
+ − 1175
succeed : 'res -> ('src -> 'res * 'src) ;
+ − 1176
fail : ('src -> 'res_src) ;
+ − 1177
!! : ('src * string option -> string) ->
+ − 1178
('src -> 'res_src) -> ('src -> 'res_src) ;
+ − 1179
\end{verbatim}
+ − 1180
\texttt{succeed r} returns \texttt{r}, with the input unchanged.
+ − 1181
\texttt{fail} always fails, raising exception \texttt{FAIL NONE}.
+ − 1182
\texttt{!! f} only affects the failure mode, turning a failure that
+ − 1183
raises \texttt{FAIL \_} into a failure that raises \texttt{ABORT ...}.
+ − 1184
This is used to prevent recovery from the failure ---
+ − 1185
thus, in \texttt{!! parse1 || parse2}, if \texttt{parse1} fails,
+ − 1186
it won't recover by trying \texttt{parse2}.
+ − 1187
+ − 1188
\begin{verbatim}
+ − 1189
one : ('si -> bool) -> ('si list -> 'si * 'si list) ;
+ − 1190
some : ('si -> 'res option) -> ('si list -> 'res * 'si list) ;
+ − 1191
\end{verbatim}
+ − 1192
These require the input to be a list of items:
+ − 1193
they fail, raising \texttt{MORE NONE} if the list is empty.
+ − 1194
On other failures they raise \texttt{FAIL NONE}
+ − 1195
+ − 1196
\texttt{one p} takes the first
+ − 1197
item from the list if it satisfies \texttt{p}, otherwise fails.
+ − 1198
+ − 1199
\texttt{some f} takes the first
+ − 1200
item from the list and applies \texttt{f} to it, failing if this returns
+ − 1201
\texttt{NONE}.
+ − 1202
+ − 1203
\begin{verbatim}
+ − 1204
many : ('si -> bool) -> 'si list -> 'si list * 'si list ;
+ − 1205
\end{verbatim}
+ − 1206
\texttt{many p} takes items from the input until it encounters one
+ − 1207
which does not satisfy \texttt{p}. If it reaches the end of the input
+ − 1208
it fails, raising \texttt{MORE NONE}.
+ − 1209
+ − 1210
\texttt{many1} (with the same type) fails if the first item
+ − 1211
does not satisfy \texttt{p}.
+ − 1212
+ − 1213
\begin{verbatim}
+ − 1214
option : ('src -> 'res * 'src) -> ('src -> 'res option * 'src)
+ − 1215
optional : ('src -> 'res * 'src) -> 'res -> ('src -> 'res * 'src)
+ − 1216
\end{verbatim}
+ − 1217
\texttt{option}:
+ − 1218
where the parser \texttt{f} succeeds with result \texttt{r}
+ − 1219
or raises \texttt{FAIL \_},
+ − 1220
\texttt{option f} gives the result \texttt{SOME r} or \texttt{NONE}.
+ − 1221
+ − 1222
\texttt{optional}: if parser \texttt{f} fails by raising \texttt{FAIL \_},
+ − 1223
\texttt{optional f default} provides the result \texttt{default}.
+ − 1224
+ − 1225
\begin{verbatim}
+ − 1226
repeat : ('src -> 'res * 'src) -> 'src -> 'res list * 'src
+ − 1227
repeat1 : ('src -> 'res * 'src) -> 'src -> 'res list * 'src
+ − 1228
bulk : ('src -> 'res * 'src) -> 'src -> 'res list * 'src
+ − 1229
\end{verbatim}
+ − 1230
\texttt{repeat f} repeatedly parses an item off the remaining input until
+ − 1231
\texttt{f} fails with \texttt{FAIL \_}
+ − 1232
+ − 1233
\texttt{repeat1} is as for \texttt{repeat}, but requires at least one
+ − 1234
successful parse.
+ − 1235
+ − 1236
\begin{verbatim}
+ − 1237
lift : ('src -> 'res * 'src) -> ('ex * 'src -> 'res * ('ex * 'src))
+ − 1238
\end{verbatim}
+ − 1239
\texttt{lift} changes the source type of a parser by putting in an extra
+ − 1240
component \texttt{'ex}, which is ignored in the parsing.
+ − 1241
+ − 1242
The \texttt{Scan} structure also provides the type \texttt{lexicon},
+ − 1243
HOW DO THEY WORK ?? TO BE COMPLETED
+ − 1244
\begin{verbatim}
+ − 1245
dest_lexicon: lexicon -> string list ;
+ − 1246
make_lexicon: string list list -> lexicon ;
+ − 1247
empty_lexicon: lexicon ;
+ − 1248
extend_lexicon: string list list -> lexicon -> lexicon ;
+ − 1249
merge_lexicons: lexicon -> lexicon -> lexicon ;
+ − 1250
is_literal: lexicon -> string list -> bool ;
+ − 1251
literal: lexicon -> string list -> string list * string list ;
+ − 1252
\end{verbatim}
+ − 1253
Two lexicons, for the commands and keywords, are stored and can be retrieved
+ − 1254
by:
+ − 1255
\begin{verbatim}
+ − 1256
val (command_lexicon, keyword_lexicon) = OuterSyntax.get_lexicons () ;
+ − 1257
val commands = Scan.dest_lexicon command_lexicon ;
+ − 1258
val keywords = Scan.dest_lexicon keyword_lexicon ;
+ − 1259
\end{verbatim}
+ − 1260
*}
+ − 1261
+ − 1262
section{* The \texttt{OuterLex} structure *}
+ − 1263
+ − 1264
text {*
+ − 1265
The source file is @{text "src/Pure/Isar/outer_lex.ML"}.
+ − 1266
In some other source files its name is abbreviated:
+ − 1267
\begin{verbatim}
+ − 1268
structure T = OuterLex;
+ − 1269
\end{verbatim}
+ − 1270
This structure defines the type \texttt{token}.
+ − 1271
(The types
+ − 1272
\texttt{OuterLex.token},
+ − 1273
\texttt{OuterParse.token} and
+ − 1274
\texttt{SpecParse.token} are all the same).
+ − 1275
+ − 1276
Input text is split up into tokens, and the input source type for many parsing
+ − 1277
functions is \texttt{token list}.
+ − 1278
220
+ − 1279
The data type definition (which is not published in the signature) is
4
+ − 1280
\begin{verbatim}
+ − 1281
datatype token = Token of Position.T * (token_kind * string);
+ − 1282
\end{verbatim}
+ − 1283
but here are some runnable examples for viewing tokens:
+ − 1284
+ − 1285
*}
+ − 1286
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1287
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1288
4
+ − 1289
69
+ − 1290
ML{*
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1291
val toks = OuterSyntax.scan Position.none
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1292
"theory,imports;begin x.y.z apply ?v1 ?'a 'a -- || 44 simp (* xx *) { * fff * }" ;
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1293
*}
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1294
69
+ − 1295
ML{*
4
+ − 1296
print_depth 20 ;
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1297
*}
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1298
69
+ − 1299
ML{*
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1300
map OuterLex.text_of toks ;
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1301
*}
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1302
69
+ − 1303
ML{*
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1304
val proper_toks = filter OuterLex.is_proper toks ;
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1305
*}
4
+ − 1306
69
+ − 1307
ML{*
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1308
map OuterLex.kind_of proper_toks
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1309
*}
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1310
69
+ − 1311
ML{*
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1312
map OuterLex.unparse proper_toks ;
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1313
*}
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1314
69
+ − 1315
ML{*
47
4daf913fdbe1
hakked latex so that it does not display ML {* *}; general tuning
Christian Urban <urbanc@in.tum.de>
diff
changeset
+ − 1316
OuterLex.stopper
4
+ − 1317
*}
+ − 1318
+ − 1319
text {*
+ − 1320
+ − 1321
The function \texttt{is\_proper : token -> bool} identifies tokens which are
+ − 1322
not white space or comments: many parsing functions assume require spaces or
+ − 1323
comments to have been filtered out.
+ − 1324
+ − 1325
There is a special end-of-file token:
+ − 1326
\begin{verbatim}
+ − 1327
val (tok_eof : token, is_eof : token -> bool) = T.stopper ;
+ − 1328
(* end of file token *)
+ − 1329
\end{verbatim}
+ − 1330
+ − 1331
*}
+ − 1332
+ − 1333
section {* The \texttt{OuterParse} structure *}
+ − 1334
+ − 1335
text {*
+ − 1336
The source file is \texttt{src/Pure/Isar/outer\_parse.ML}.
+ − 1337
In some other source files its name is abbreviated:
+ − 1338
\begin{verbatim}
+ − 1339
structure P = OuterParse;
+ − 1340
\end{verbatim}
+ − 1341
Here the parsers use \texttt{token list} as the input source type.
+ − 1342
+ − 1343
Some of the parsers simply select the first token, provided that it is of the
+ − 1344
right kind (as returned by \texttt{T.kind\_of}): these are
+ − 1345
\texttt{ command, keyword, short\_ident, long\_ident, sym\_ident, term\_var,
+ − 1346
type\_ident, type\_var, number, string, alt\_string, verbatim, sync, eof}
+ − 1347
Others select the first token, provided that it is one of several kinds,
+ − 1348
(eg, \texttt{name, xname, text, typ}).
+ − 1349
+ − 1350
\begin{verbatim}
+ − 1351
type 'a tlp = token list -> 'a * token list ; (* token list parser *)
+ − 1352
$$$ : string -> string tlp
+ − 1353
nat : int tlp ;
+ − 1354
maybe : 'a tlp -> 'a option tlp ;
+ − 1355
\end{verbatim}
+ − 1356
+ − 1357
\texttt{\$\$\$ s} returns the first token,
+ − 1358
if it equals \texttt{s} \emph{and} \texttt{s} is a keyword.
+ − 1359
+ − 1360
\texttt{nat} returns the first token, if it is a number, and evaluates it.
+ − 1361
+ − 1362
\texttt{maybe}: if \texttt{p} returns \texttt{r},
+ − 1363
then \texttt{maybe p} returns \texttt{SOME r} ;
+ − 1364
if the first token is an underscore, it returns \texttt{NONE}.
+ − 1365
+ − 1366
A few examples:
+ − 1367
\begin{verbatim}
+ − 1368
P.list : 'a tlp -> 'a list tlp ; (* likewise P.list1 *)
+ − 1369
P.and_list : 'a tlp -> 'a list tlp ; (* likewise P.and_list1 *)
+ − 1370
val toks : token list = OuterSyntax.scan "44 ,_, 66,77" ;
+ − 1371
val proper_toks = List.filter T.is_proper toks ;
+ − 1372
P.list P.nat toks ; (* OK, doesn't recognize white space *)
+ − 1373
P.list P.nat proper_toks ; (* fails, doesn't recognize what follows ',' *)
+ − 1374
P.list (P.maybe P.nat) proper_toks ; (* fails, end of input *)
+ − 1375
P.list (P.maybe P.nat) (proper_toks @ [tok_eof]) ; (* OK *)
+ − 1376
val toks : token list = OuterSyntax.scan "44 and 55 and 66 and 77" ;
+ − 1377
P.and_list P.nat (List.filter T.is_proper toks @ [tok_eof]) ; (* ??? *)
+ − 1378
\end{verbatim}
+ − 1379
+ − 1380
The following code helps run examples:
+ − 1381
\begin{verbatim}
+ − 1382
fun parse_str tlp str =
+ − 1383
let val toks : token list = OuterSyntax.scan str ;
+ − 1384
val proper_toks = List.filter T.is_proper toks @ [tok_eof] ;
+ − 1385
val (res, rem_toks) = tlp proper_toks ;
+ − 1386
val rem_str = String.concat
+ − 1387
(Library.separate " " (List.map T.unparse rem_toks)) ;
+ − 1388
in (res, rem_str) end ;
+ − 1389
\end{verbatim}
+ − 1390
+ − 1391
Some examples from \texttt{src/Pure/Isar/outer\_parse.ML}
+ − 1392
\begin{verbatim}
+ − 1393
val type_args =
+ − 1394
type_ident >> Library.single ||
+ − 1395
$$$ "(" |-- !!! (list1 type_ident --| $$$ ")") ||
+ − 1396
Scan.succeed [];
+ − 1397
\end{verbatim}
+ − 1398
There are three ways parsing a list of type arguments can succeed.
+ − 1399
The first line reads a single type argument, and turns it into a singleton
+ − 1400
list.
+ − 1401
The second line reads "(", and then the remainder, ignoring the "(" ;
+ − 1402
the remainder consists of a list of type identifiers (at least one),
+ − 1403
and then a ")" which is also ignored.
+ − 1404
The \texttt{!!!} ensures that if the parsing proceeds this far and then fails,
+ − 1405
it won't try the third line (see the description of \texttt{Scan.!!}).
+ − 1406
The third line consumes no input and returns the empty list.
+ − 1407
+ − 1408
\begin{verbatim}
+ − 1409
fun triple2 (x, (y, z)) = (x, y, z);
+ − 1410
val arity = xname -- ($$$ "::" |-- !!! (
+ − 1411
Scan.optional ($$$ "(" |-- !!! (list1 sort --| $$$ ")")) []
+ − 1412
-- sort)) >> triple2;
+ − 1413
\end{verbatim}
+ − 1414
The parser \texttt{arity} reads a typename $t$, then ``\texttt{::}'' (which is
+ − 1415
ignored), then optionally a list $ss$ of sorts and then another sort $s$.
+ − 1416
The result $(t, (ss, s))$ is transformed by \texttt{triple2} to $(t, ss, s)$.
+ − 1417
The second line reads the optional list of sorts:
+ − 1418
it reads first ``\texttt{(}'' and last ``\texttt{)}'', which are both ignored,
+ − 1419
and between them a comma-separated list of sorts.
+ − 1420
If this list is absent, the default \texttt{[]} provides the list of sorts.
+ − 1421
+ − 1422
\begin{verbatim}
+ − 1423
parse_str P.type_args "('a, 'b) ntyp" ;
+ − 1424
parse_str P.type_args "'a ntyp" ;
+ − 1425
parse_str P.type_args "ntyp" ;
+ − 1426
parse_str P.arity "ty :: tycl" ;
+ − 1427
parse_str P.arity "ty :: (tycl1, tycl2) tycl" ;
+ − 1428
\end{verbatim}
+ − 1429
+ − 1430
*}
+ − 1431
+ − 1432
section {* The \texttt{SpecParse} structure *}
+ − 1433
+ − 1434
text {*
+ − 1435
The source file is \texttt{src/Pure/Isar/spec\_parse.ML}.
+ − 1436
This structure contains token list parsers for more complicated values.
+ − 1437
For example,
+ − 1438
\begin{verbatim}
+ − 1439
open SpecParse ;
+ − 1440
attrib : Attrib.src tok_rdr ;
+ − 1441
attribs : Attrib.src list tok_rdr ;
+ − 1442
opt_attribs : Attrib.src list tok_rdr ;
+ − 1443
xthm : (thmref * Attrib.src list) tok_rdr ;
+ − 1444
xthms1 : (thmref * Attrib.src list) list tok_rdr ;
+ − 1445
+ − 1446
parse_str attrib "simp" ;
+ − 1447
parse_str opt_attribs "hello" ;
+ − 1448
val (ass, "") = parse_str attribs "[standard, xxxx, simp, intro, OF sym]" ;
+ − 1449
map Args.dest_src ass ;
+ − 1450
val (asrc, "") = parse_str attrib "THEN trans [THEN sym]" ;
+ − 1451
+ − 1452
parse_str xthm "mythm [attr]" ;
+ − 1453
parse_str xthms1 "thm1 [attr] thms2" ;
+ − 1454
\end{verbatim}
+ − 1455
+ − 1456
As you can see, attributes are described using types of the \texttt{Args}
+ − 1457
structure, described below.
+ − 1458
*}
+ − 1459
+ − 1460
section{* The \texttt{Args} structure *}
+ − 1461
+ − 1462
text {*
+ − 1463
The source file is \texttt{src/Pure/Isar/args.ML}.
220
+ − 1464
The primary type of this structure is the \texttt{src} data type;
4
+ − 1465
the single constructors not published in the signature, but
+ − 1466
\texttt{Args.src} and \texttt{Args.dest\_src}
+ − 1467
are in fact the constructor and destructor functions.
+ − 1468
Note that the types \texttt{Attrib.src} and \texttt{Method.src}
+ − 1469
are in fact \texttt{Args.src}.
+ − 1470
+ − 1471
\begin{verbatim}
+ − 1472
src : (string * Args.T list) * Position.T -> Args.src ;
+ − 1473
dest_src : Args.src -> (string * Args.T list) * Position.T ;
+ − 1474
Args.pretty_src : Proof.context -> Args.src -> Pretty.T ;
+ − 1475
fun pr_src ctxt src = Pretty.string_of (Args.pretty_src ctxt src) ;
+ − 1476
+ − 1477
val thy = ML_Context.the_context () ;
+ − 1478
val ctxt = ProofContext.init thy ;
+ − 1479
map (pr_src ctxt) ass ;
+ − 1480
\end{verbatim}
+ − 1481
+ − 1482
So an \texttt{Args.src} consists of the first word, then a list of further
+ − 1483
``arguments'', of type \texttt{Args.T}, with information about position in the
+ − 1484
input.
+ − 1485
\begin{verbatim}
+ − 1486
(* how an Args.src is parsed *)
+ − 1487
P.position : 'a tlp -> ('a * Position.T) tlp ;
+ − 1488
P.arguments : Args.T list tlp ;
+ − 1489
+ − 1490
val parse_src : Args.src tlp =
+ − 1491
P.position (P.xname -- P.arguments) >> Args.src ;
+ − 1492
\end{verbatim}
+ − 1493
+ − 1494
\begin{verbatim}
+ − 1495
val ((first_word, args), pos) = Args.dest_src asrc ;
+ − 1496
map Args.string_of args ;
+ − 1497
\end{verbatim}
+ − 1498
+ − 1499
The \texttt{Args} structure contains more parsers and parser transformers
+ − 1500
for which the input source type is \texttt{Args.T list}. For example,
+ − 1501
\begin{verbatim}
+ − 1502
type 'a atlp = Args.T list -> 'a * Args.T list ;
+ − 1503
open Args ;
+ − 1504
nat : int atlp ; (* also Args.int *)
+ − 1505
thm_sel : PureThy.interval list atlp ;
+ − 1506
list : 'a atlp -> 'a list atlp ;
+ − 1507
attribs : (string -> string) -> Args.src list atlp ;
+ − 1508
opt_attribs : (string -> string) -> Args.src list atlp ;
+ − 1509
+ − 1510
(* parse_atl_str : 'a atlp -> (string -> 'a * string) ;
+ − 1511
given an Args.T list parser, to get a string parser *)
+ − 1512
fun parse_atl_str atlp str =
+ − 1513
let val (ats, rem_str) = parse_str P.arguments str ;
+ − 1514
val (res, rem_ats) = atlp ats ;
+ − 1515
in (res, String.concat (Library.separate " "
+ − 1516
(List.map Args.string_of rem_ats @ [rem_str]))) end ;
+ − 1517
+ − 1518
parse_atl_str Args.int "-1-," ;
+ − 1519
parse_atl_str (Scan.option Args.int) "x1-," ;
+ − 1520
parse_atl_str Args.thm_sel "(1-,4,13-22)" ;
+ − 1521
+ − 1522
val (ats as atsrc :: _, "") = parse_atl_str (Args.attribs I)
+ − 1523
"[THEN trans [THEN sym], simp, OF sym]" ;
+ − 1524
\end{verbatim}
+ − 1525
+ − 1526
From here, an attribute is interpreted using \texttt{Attrib.attribute}.
+ − 1527
+ − 1528
\texttt{Args} has a large number of functions which parse an \texttt{Args.src}
+ − 1529
and also refer to a generic context.
+ − 1530
Note the use of \texttt{Scan.lift} for this.
+ − 1531
(as does \texttt{Attrib} - RETHINK THIS)
+ − 1532
+ − 1533
(\texttt{Args.syntax} shown below has type specialised)
+ − 1534
+ − 1535
\begin{verbatim}
+ − 1536
type ('res, 'src) parse_fn = 'src -> 'res * 'src ;
+ − 1537
type 'a cgatlp = ('a, Context.generic * Args.T list) parse_fn ;
+ − 1538
Scan.lift : 'a atlp -> 'a cgatlp ;
+ − 1539
term : term cgatlp ;
+ − 1540
typ : typ cgatlp ;
+ − 1541
+ − 1542
Args.syntax : string -> 'res cgatlp -> src -> ('res, Context.generic) parse_fn ;
+ − 1543
Attrib.thm : thm cgatlp ;
+ − 1544
Attrib.thms : thm list cgatlp ;
+ − 1545
Attrib.multi_thm : thm list cgatlp ;
+ − 1546
+ − 1547
(* parse_cgatl_str : 'a cgatlp -> (string -> 'a * string) ;
+ − 1548
given a (Context.generic * Args.T list) parser, to get a string parser *)
+ − 1549
fun parse_cgatl_str cgatlp str =
+ − 1550
let
+ − 1551
(* use the current generic context *)
+ − 1552
val generic = Context.Theory thy ;
+ − 1553
val (ats, rem_str) = parse_str P.arguments str ;
+ − 1554
(* ignore any change to the generic context *)
+ − 1555
val (res, (_, rem_ats)) = cgatlp (generic, ats) ;
+ − 1556
in (res, String.concat (Library.separate " "
+ − 1557
(List.map Args.string_of rem_ats @ [rem_str]))) end ;
+ − 1558
\end{verbatim}
+ − 1559
*}
+ − 1560
+ − 1561
section{* Attributes, and the \texttt{Attrib} structure *}
+ − 1562
+ − 1563
text {*
+ − 1564
The type \texttt{attribute} is declared in \texttt{src/Pure/thm.ML}.
+ − 1565
The source file for the \texttt{Attrib} structure is
+ − 1566
\texttt{src/Pure/Isar/attrib.ML}.
+ − 1567
Most attributes use a theorem to change a generic context (for example,
+ − 1568
by declaring that the theorem should be used, by default, in simplification),
+ − 1569
or change a theorem (which most often involves referring to the current
+ − 1570
theory).
+ − 1571
The functions \texttt{Thm.rule\_attribute} and
+ − 1572
\texttt{Thm.declaration\_attribute} create attributes of these kinds.
+ − 1573
+ − 1574
\begin{verbatim}
+ − 1575
type attribute = Context.generic * thm -> Context.generic * thm;
+ − 1576
type 'a trf = 'a -> 'a ; (* transformer of a given type *)
+ − 1577
Thm.rule_attribute : (Context.generic -> thm -> thm) -> attribute ;
+ − 1578
Thm.declaration_attribute : (thm -> Context.generic trf) -> attribute ;
+ − 1579
+ − 1580
Attrib.print_attributes : theory -> unit ;
+ − 1581
Attrib.pretty_attribs : Proof.context -> src list -> Pretty.T list ;
+ − 1582
+ − 1583
List.app Pretty.writeln (Attrib.pretty_attribs ctxt ass) ;
+ − 1584
\end{verbatim}
+ − 1585
+ − 1586
An attribute is stored in a theory as indicated by:
+ − 1587
\begin{verbatim}
+ − 1588
Attrib.add_attributes :
+ − 1589
(bstring * (src -> attribute) * string) list -> theory trf ;
+ − 1590
(*
+ − 1591
Attrib.add_attributes [("THEN", THEN_att, "resolution with rule")] ;
+ − 1592
*)
+ − 1593
\end{verbatim}
+ − 1594
where the first and third arguments are name and description of the attribute,
+ − 1595
and the second is a function which parses the attribute input text
+ − 1596
(including the attribute name, which has necessarily already been parsed).
+ − 1597
Here, \texttt{THEN\_att} is a function declared in the code for the
+ − 1598
structure \texttt{Attrib}, but not published in its signature.
+ − 1599
The source file \texttt{src/Pure/Isar/attrib.ML} shows the use of
+ − 1600
\texttt{Attrib.add\_attributes} to add a number of attributes.
+ − 1601
+ − 1602
\begin{verbatim}
+ − 1603
FullAttrib.THEN_att : src -> attribute ;
+ − 1604
FullAttrib.THEN_att atsrc (generic, ML_Context.thm "sym") ;
+ − 1605
FullAttrib.THEN_att atsrc (generic, ML_Context.thm "all_comm") ;
+ − 1606
\end{verbatim}
+ − 1607
+ − 1608
\begin{verbatim}
+ − 1609
Attrib.syntax : attribute cgatlp -> src -> attribute ;
+ − 1610
Attrib.no_args : attribute -> src -> attribute ;
+ − 1611
\end{verbatim}
+ − 1612
When this is called as \texttt{syntax scan src (gc, th)}
+ − 1613
the generic context \texttt{gc} is used
+ − 1614
(and potentially changed to \texttt{gc'})
+ − 1615
by \texttt{scan} in parsing to obtain an attribute \texttt{attr} which would
+ − 1616
then be applied to \texttt{(gc', th)}.
+ − 1617
The source for parsing the attribute is the arguments part of \texttt{src},
+ − 1618
which must all be consumed by the parse.
+ − 1619
+ − 1620
For example, for \texttt{Attrib.no\_args attr src}, the attribute parser
+ − 1621
simply returns \texttt{attr}, requiring that the arguments part of
+ − 1622
\texttt{src} must be empty.
+ − 1623
+ − 1624
Some examples from \texttt{src/Pure/Isar/attrib.ML}, modified:
+ − 1625
\begin{verbatim}
+ − 1626
fun rot_att_n n (gc, th) = (gc, rotate_prems n th) ;
+ − 1627
rot_att_n : int -> attribute ;
+ − 1628
val rot_arg = Scan.lift (Scan.optional Args.int 1 : int atlp) : int cgatlp ;
+ − 1629
val rotated_att : src -> attribute =
+ − 1630
Attrib.syntax (rot_arg >> rot_att_n : attribute cgatlp) ;
+ − 1631
+ − 1632
val THEN_arg : int cgatlp = Scan.lift
+ − 1633
(Scan.optional (Args.bracks Args.nat : int atlp) 1 : int atlp) ;
+ − 1634
+ − 1635
Attrib.thm : thm cgatlp ;
+ − 1636
+ − 1637
THEN_arg -- Attrib.thm : (int * thm) cgatlp ;
+ − 1638
+ − 1639
fun THEN_att_n (n, tht) (gc, th) = (gc, th RSN (n, tht)) ;
+ − 1640
THEN_att_n : int * thm -> attribute ;
+ − 1641
+ − 1642
val THEN_att : src -> attribute = Attrib.syntax
+ − 1643
(THEN_arg -- Attrib.thm >> THEN_att_n : attribute cgatlp);
+ − 1644
\end{verbatim}
+ − 1645
The functions I've called \texttt{rot\_arg} and \texttt{THEN\_arg}
+ − 1646
read an optional argument, which for \texttt{rotated} is an integer,
+ − 1647
and for \texttt{THEN} is a natural enclosed in square brackets;
+ − 1648
the default, if the argument is absent, is 1 in each case.
+ − 1649
Functions \texttt{rot\_att\_n} and \texttt{THEN\_att\_n} turn these into
+ − 1650
attributes, where \texttt{THEN\_att\_n} also requires a theorem, which is
+ − 1651
parsed by \texttt{Attrib.thm}.
+ − 1652
Infix operators \texttt{--} and \texttt{>>} are in the structure \texttt{Scan}.
+ − 1653
+ − 1654
*}
+ − 1655
+ − 1656
section{* Methods, and the \texttt{Method} structure *}
+ − 1657
+ − 1658
text {*
+ − 1659
The source file is \texttt{src/Pure/Isar/method.ML}.
+ − 1660
The type \texttt{method} is defined by the datatype declaration
+ − 1661
\begin{verbatim}
+ − 1662
(* datatype method = Meth of thm list -> cases_tactic; *)
+ − 1663
RuleCases.NO_CASES : tactic -> cases_tactic ;
+ − 1664
\end{verbatim}
+ − 1665
In fact \texttt{RAW\_METHOD\_CASES} (below) is exactly the constructor
+ − 1666
\texttt{Meth}.
+ − 1667
A \texttt{cases\_tactic} is an elaborated version of a tactic.
+ − 1668
\texttt{NO\_CASES tac} is a \texttt{cases\_tactic} which consists of a
+ − 1669
\texttt{cases\_tactic} without any further case information.
+ − 1670
For further details see the description of structure \texttt{RuleCases} below.
+ − 1671
The list of theorems to be passed to a method consists of the current
+ − 1672
\emph{facts} in the proof.
+ − 1673
+ − 1674
\begin{verbatim}
+ − 1675
RAW_METHOD : (thm list -> tactic) -> method ;
+ − 1676
METHOD : (thm list -> tactic) -> method ;
+ − 1677
+ − 1678
SIMPLE_METHOD : tactic -> method ;
+ − 1679
SIMPLE_METHOD' : (int -> tactic) -> method ;
+ − 1680
SIMPLE_METHOD'' : ((int -> tactic) -> tactic) -> (int -> tactic) -> method ;
+ − 1681
+ − 1682
RAW_METHOD_CASES : (thm list -> cases_tactic) -> method ;
+ − 1683
METHOD_CASES : (thm list -> cases_tactic) -> method ;
+ − 1684
\end{verbatim}
+ − 1685
A method is, in its simplest form, a tactic; applying the method is to apply
+ − 1686
the tactic to the current goal state.
+ − 1687
+ − 1688
Applying \texttt{RAW\_METHOD tacf} creates a tactic by applying
+ − 1689
\texttt{tacf} to the current {facts}, and applying that tactic to the
+ − 1690
goal state.
+ − 1691
+ − 1692
\texttt{METHOD} is similar but also first applies
+ − 1693
\texttt{Goal.conjunction\_tac} to all subgoals.
+ − 1694
+ − 1695
\texttt{SIMPLE\_METHOD tac} inserts the facts into all subgoals and then
+ − 1696
applies \texttt{tacf}.
+ − 1697
+ − 1698
\texttt{SIMPLE\_METHOD' tacf} inserts the facts and then
+ − 1699
applies \texttt{tacf} to subgoal 1.
+ − 1700
+ − 1701
\texttt{SIMPLE\_METHOD'' quant tacf} does this for subgoal(s) selected by
+ − 1702
\texttt{quant}, which may be, for example,
+ − 1703
\texttt{ALLGOALS} (all subgoals),
+ − 1704
\texttt{TRYALL} (try all subgoals, failure is OK),
+ − 1705
\texttt{FIRSTGOAL} (try subgoals until it succeeds once),
+ − 1706
\texttt{(fn tacf => tacf 4)} (subgoal 4), etc
16
+ − 1707
(see the \texttt{Tactical} structure, FIXME) %%\cite[Chapter 4]{ref}).
4
+ − 1708
+ − 1709
A method is stored in a theory as indicated by:
+ − 1710
\begin{verbatim}
+ − 1711
Method.add_method :
+ − 1712
(bstring * (src -> Proof.context -> method) * string) -> theory trf ;
+ − 1713
( *
+ − 1714
* )
+ − 1715
\end{verbatim}
+ − 1716
where the first and third arguments are name and description of the method,
+ − 1717
and the second is a function which parses the method input text
+ − 1718
(including the method name, which has necessarily already been parsed).
+ − 1719
+ − 1720
Here, \texttt{xxx} is a function declared in the code for the
+ − 1721
structure \texttt{Method}, but not published in its signature.
+ − 1722
The source file \texttt{src/Pure/Isar/method.ML} shows the use of
+ − 1723
\texttt{Method.add\_method} to add a number of methods.
+ − 1724
+ − 1725
+ − 1726
*}
75
+ − 1727
(*>*)
220
+ − 1728
end