This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: New module system wishlist
- To: Neil Jerram <neil at ossau dot uklinux dot net>
- Subject: Re: New module system wishlist
- From: Jost Boekemeier <jostobfe at linux dot zrz dot TU-Berlin dot DE>
- Date: 24 Jan 2000 18:22:37 +0100
- Cc: djurfeldt at nada dot kth dot se, guile at sourceware dot cygnus dot com
- References: <E12AixQ-00062S-00@mdj.nada.kth.se> <200001221141.LAA00475@ossau>
Neil Jerram <neil@ossau.uklinux.net> writes:
> * cleanliness:
>
> A module should be able to be totally clean. There should be no
> need to have *any* extra bindings in a module (a la
> %module-interface or `define-module').
>
> What is the define-module binding for in the current module system?
It creates a "temporary" module. I think that define-module
should be removed or it should be extended so that it creates
a real (permanent) module.
> Sorry, I don't understand this at all. Could you explain further?
Check out my module patch and type this:
(module-open )
Now try to leave the current module and return to the
config module. (yes, a "killall guile" issued from another
console still works, but that's not exactly user
friendly).
Two solutions:
1) Always create a repl per module and let the user get back to the
config module by pressing Control-D
2) Use only one repl and introduce special ",xxx" commands which will
be interpreted by the repl.
Jost