Use liarc built-in objects only for LOAD, not for FASLOAD. When we're
authorTaylor R. Campbell <net/mumble/campbell>
Sun, 15 Apr 2007 07:49:50 +0000 (07:49 +0000)
committerTaylor R. Campbell <net/mumble/campbell>
Sun, 15 Apr 2007 07:49:50 +0000 (07:49 +0000)
commitc4bc216d5196f1a3148712ca98122013dca57de0
tree46032af44b71de648c30515ad5dd3cae5756f679
parentc553093eea37cf48057675f6a3581115741b65c3
Use liarc built-in objects only for LOAD, not for FASLOAD.  When we're
actually loading code for execution, we need them; when we're loading
code for data (e.g., when loading scode for the compiler -- especially
when it is compiling itself, or other parts of the system that are
loaded into the compiler image), we need the file and not the compiled
expression statically linked into the microcode.

This is a kludge, but it is necessary for bootstrapping liarc.  I
don't know whether there is any code that relies on FASLOAD yielding
built-in objects, however; I suspect not.
v7/src/runtime/load.scm