The variable *interactive* determines whether the SCM session is interactive, or should quit after the command line is processed. *interactive* is controlled directly by the command-line options ‘-b’, ‘-i’, and ‘-s’ (see Invoking SCM). If none of these options are specified, the rules to determine interactivity are more complicated; see Init5e7.scm for details.
Restarts the SCM program with the same arguments as it was originally invoked. All ‘-l’ loaded files are loaded again; If those files have changed, those changes will be reflected in the new session.
Note When running a saved executable (see Dump),
restartis redefined to be
Exits and immediately re-invokes the same executable with the same arguments. If the executable file has been changed or replaced since the beginning of the current session, the new executable will be invoked. This differentiates
Controls how much monitoring information is printed. If n is:
- no prompt or information is printed.
- >= 1
- a prompt is printed.
- >= 2
- messages bracketing file loading are printed.
- >= 3
- the CPU time is printed after each top level form evaluated; notifications of heap growth printed; the interpreter checks stack depth periodically.
- >= 4
- a garbage collection summary is printed after each top level form evaluated;
- >= 5
- a message for each GC (see Garbage Collection) is printed; warnings issued for top-level symbols redefined.
Scans all of SCM objects and reclaims for further use those that are no longer accessible.
Prints out statistics about SCM's current use of storage.
(room #t)also gives the hexadecimal heap segment and stack bounds.
In order to dump a saved executable or to dynamically-link using DLD,
SCM must know where its executable file is. Sometimes SCM
(see Executable Pathname) guesses incorrectly the location of the
currently running executable. In that case, the correct path can be set
execpath with the pathname.
For other configuration constants and procedures See Configuration.