File: get_steps.doc

package info (click to toggle)
hol88 2.02.19940316-33
  • links: PTS
  • area: main
  • in suites: stretch
  • size: 65,988 kB
  • ctags: 21,623
  • sloc: ml: 199,939; ansic: 9,666; sh: 7,118; makefile: 6,095; lisp: 2,747; yacc: 894; sed: 201; cpp: 87; awk: 5
file content (74 lines) | stat: -rw-r--r-- 2,100 bytes parent folder | download | duplicates (22)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
\DOC get_steps

\TYPE {get_steps : void -> step list}

\KEYWORDS
proof recording.


\SYNOPSIS
Get the proof steps since last time the proof recorder is enabled.

\DESCRIBE
A proof is a list of inference steps. After the proof recorder is
enabled, every inference performed by the system is recorded and
cumulated in an internal buffer. When a proof is completed, the raw
records can then be processed and output to a disk file.

{get_steps} is a low level user function for managing the proof
recorder. It returns the list of steps cumulated since last time the
proof recorder is enabled, i.e. the function {record_proof} is called
with the value {true}. The list of inference step needs to be
processed to produce a proof line list which can be output to a file.


\FAILURE
Never fail.

\EXAMPLE
Below is an example showing how to record an extremely simple proof
in which the function {get_steps} is called to get the list of
inference steps:
{
#let th = SPEC_ALL ADD_SYM;;
Theorem ADD_SYM autoloading from theory `arithmetic` ...
ADD_SYM = |- !m n. m + n = n + m

th = |- m + n = n + m

#let v = genvar ":num";;
"GEN%VAR%536" : term

#record_proof true;;
() : void

#let th1 = (REFL "SUC(m + n)");;
th1 = |- SUC(m + n) = SUC(m + n)

#let th2 = SUBST [th,v] "SUC(m + n) = SUC ^v" th1;;
th2 = |- SUC(m + n) = SUC(n + m)

#record_proof false;;
() : void

#write_proof_to `ap_term.prf` `ap_term` [] (get_steps());;
() : void
}
The proof consists of two inference steps: the application of the two
primitive inference rules {REFL} and {SUBST}. The function
{write_proof_to} outputs the proof into a file names {ap_term.prf}.

\COMMENTS
This function is used to implement higher level user functions for
recording proof in the library {record_proof}. It is much more
convenient to use those functions than the low level functions
such as {get_steps} directly.

\SEEALSO
record_proof, is_recording_proof, RecordStep, 
suspend_recording, resume_recording, MakeProof,
current_proof, current_proof_file,
new_proof_file, close_proof_file, begin_proof, end_proof,
TAC_PROOF, PROVE, prove, prove_thm.

\ENDDOC