Age | Commit message (Collapse) | Author |
|
1) The loader and system modules are loaded by the C directly into the user module
2) The system module is then loaded with the loader from the user module
3) The loader module is then loaded with the loader from the user module
4) The repl is then loaded with the loader from the loader module
5) The user module is cleared
|
|
|
|
goals too
|
|
using the dynamic/1 predicate
|
|
|
|
clausenr in call/1, so cuts are local to that call
|
|
contains parts that cannot be called, but it is
OK for parts of G to be variables, such as G=(write(hey), X).
|
|
|
|
|
|
|
|
|
|
|
|
current_prolog_flag/2
|
|
|
|
|
|
prettyprint code, used by write_term
|
|
variables(Vars),
variable_names(VarNames),
singletons(Singles)
as required per the ISO standard
|
|
|
|
|
|
retract/1 but doesn't backtrack)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
tells us something about term types. Should be used a lot more instead of explicitly looking into terms->tag everywhere
|
|
|
|
|
|
|
|
|
|
leave behind some bindings even though the unification failed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
which defines how double quoted strings are stored.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
actual builtins
|
|
|