Age | Commit message (Collapse) | Author |
|
|
|
the correct module to pick up the correct operators
|
|
This makes sure that the system doesn't appear slow after a potentially very
simple first query
|
|
|
|
being local in a call
|
|
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
|
|
|
|
mis-spelling
|
|
|
|
|
|
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).
|
|
|
|
|
|
operator
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
current_prolog_flag/2
|
|
|
|
|
|
|
|
prettyprint code, used by write_term
|
|
variables(Vars),
variable_names(VarNames),
singletons(Singles)
as required per the ISO standard
|
|
|
|
|
|
|
|
|
|
lowest clause number
|
|
pick it with = instead
|
|
|
|
|
|
retract/1 but doesn't backtrack)
|
|
|
|
about them
|
|
|