This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Problems with tguile's unexec
- To: guile at sourceware dot cygnus dot com
- Subject: Problems with tguile's unexec
- From: Greg Badros <gjb at cs dot washington dot edu>
- Date: 17 Oct 1999 18:28:29 -0700
When I do:
tguile --dump guile-all test-all.scm # (see below for test-all.scm)
and then run ./guile-all, I get a prompt that looks like:
guile> <s
^ actually the <= single glyph character
and before every printed response I get
<f
^ same <= single glyph character
For example, below, I entered "4" into the prompt:
guile> <s 4
<f4
Also, I'm confused about why I have to run `load-all-modules' again
after starting ./guile-all before the procedures are visible. Can
anyone explain this to me?
Incidentally, is there a good way to write a module that exports symbols
from a bunch of modules that it imports? E.g., a single module
guile-all.scm that does the use-modules, and then another module can
just use that one module and get at all the symbols?
Finally, how robust is unexec? What's the probability that I'd be able
to use the code from tguile-core.c embedded in Scwm and get Scwm to be
able to dump itself after loading a bunch of its modules?
Thanks,
Greg
test-all.scm:
(define-public (load-all-modules)
(use-modules
(ice-9 and-let*)
(ice-9 calling)
(ice-9 common-list)
(ice-9 debug)
(ice-9 debugger)
(ice-9 emacs)
(ice-9 expect)
(ice-9 format)
(ice-9 getopt-gnu-style)
(ice-9 getopt-long)
(ice-9 hcons)
(ice-9 lineio)
(ice-9 ls)
(ice-9 mapping)
(ice-9 optargs)
(ice-9 poe)
(ice-9 popen)
(ice-9 q)
(ice-9 regex)
(ice-9 runq)
(ice-9 session)
(ice-9 streams)
(ice-9 string-fun)
(ice-9 syncase)
(ice-9 slib)
(ice-9 tags)
(ice-9 threads)))
(load-all-modules)