72 lines
2.4 KiB
Plaintext
72 lines
2.4 KiB
Plaintext
|
I have hacked the following files to accomodate my new top-level. Most
|
||
|
changes are to allow non-noisy file and package loading, which is not
|
||
|
acceptable for scripts.
|
||
|
-Olin
|
||
|
6/95
|
||
|
|
||
|
env/load-package.scm
|
||
|
really-ensure-loaded
|
||
|
New proc, has noise option.
|
||
|
|
||
|
bcomp/undefined.scm
|
||
|
really-noting-undefined-variables
|
||
|
New proc, has noise option.
|
||
|
|
||
|
bcomp/scan.scm
|
||
|
really-scan-structures
|
||
|
really-scan-file
|
||
|
really-scan-package
|
||
|
New procs, have noise option.
|
||
|
|
||
|
rts/eval.scm
|
||
|
really-eval-scanned-forms
|
||
|
New proc, has noise option.
|
||
|
N.B.: While there is another implementation of EVAL-SCANNED-FORMS
|
||
|
(in debug/mini-eval), I didn't bother to define REALLY-E-S-F over
|
||
|
there as well.
|
||
|
|
||
|
env/build.scm
|
||
|
STAND-ALONE-RESUMER now uses ERROR-OUTPUT-PORT
|
||
|
for default error reporting, not CURRENT-OUTPUT-PORT.
|
||
|
|
||
|
|
||
|
more-packages.scm
|
||
|
- Had to add ports to BUILD's open clause, so it could get at
|
||
|
ERROR-OUTPUT-PORTS
|
||
|
- Added a structure BUILD-INTERNALS exporting SIMPLE-CONDITION-HANDLER.
|
||
|
This is for the top-levels made by the scsh heap dumpers (as a
|
||
|
workaround for S48 error-output-port lossage).
|
||
|
Also must add BUILD-INTERNALS to
|
||
|
MORE-STRUCTURES-INTERFACE at end of file so it'll be kept around.
|
||
|
|
||
|
more-interfaces.scm
|
||
|
Added USER-ENVIRONMENT to package-commands-internal-interface.
|
||
|
My top-level needs it.
|
||
|
|
||
|
build-usual-image
|
||
|
Changed to fire up vm as
|
||
|
vm -o vm -i initial.image batch
|
||
|
not
|
||
|
vm -i initial.image -a batch
|
||
|
The nature of Unix args and the recursive-machine structure
|
||
|
of arglists means that -i <image> *must* terminate vm arg scanning.
|
||
|
So the -a is superfluous.
|
||
|
|
||
|
command.scm
|
||
|
with-new-session, with-user-context
|
||
|
New procedures, separate the idea of "logging in" user --
|
||
|
establishing context for command processor -- from actually
|
||
|
starting up the command processor. The old START-COMMAND-PROCESSOR
|
||
|
folded these two together, so you can't establish context and
|
||
|
then run your own thunk. (You want to do this if your top-level
|
||
|
thunk might later hit a breakpoint, for instance.)
|
||
|
These are also exported in whatever the right package is.
|
||
|
|
||
|
initial-packages.scm
|
||
|
Added really-ensure-loaded to ENSURES-LOADED package.
|
||
|
|
||
|
interfaces.scm
|
||
|
Added really-{scan-structures,noting-undefined-variables,
|
||
|
eval-scanned-forms} to the interfaces containing the
|
||
|
non-really variants.
|