File: implementation_notes.org

package info (click to toggle)
eprover 3.2.5%2Bds-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 14,504 kB
  • sloc: ansic: 104,396; csh: 13,135; python: 11,207; awk: 5,825; makefile: 554; sh: 400
file content (28 lines) | stat: -rw-r--r-- 906 bytes parent folder | download
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
* Terms

** Symbol representation

- Term cells carry an f_code
- Positive f_codes represent function and predicate symbols, and are
  indices into the signature tables (but see below for DB-Vars)
- Negative f_codes represent variables, and index into a VarBank.
  Permanent clauses only use odd f_codes (-2, -4, ..)
  Every normal variable is paired with a "fresh" variable (-1, -3,
  ...)
  These are only used in the copy of the given clause used as the
  "new" premise of inferences (the other clause being a "permanent"
  clause)

** Higher-Order terms

*** Flat-Spine-Notation

- Terms are _not_ fully curried, but as flat as possible.
  f @ a @ b @ c is represented as f(a,b,c) (even if arity(f)=5!)
- Applied variables use the apply-Operator
  X @ a @ b @c is represented as @(X, a, b, c)

*** Lambdas

- De-Bruin-Variables are represented in a second variable bank, and
  use positive (!) f_codes