This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: About modules
- To: jostobfe at calvados dot zrz dot TU-Berlin dot DE
- Subject: Re: About modules
- From: Clark McGrew <mcgrew at ale dot physics dot sunysb dot edu>
- Date: Wed, 08 Mar 2000 13:26:02 -0500
- CC: clark dot mcgrew at sunysb dot edu, guile at sourceware dot cygnus dot com
- References: <E12SRDh-0000SR-00@boxer.physics.sunysb.edu> <p2thfehlafe.fsf@apfel.zrz.tu-berlin.de>
- Reply-to: clark dot mcgrew at sunysb dot edu
>>>>> "Jost" == Jost Boekemeier <jostobfe@calvados.zrz.TU-Berlin.DE> writes:
Jost> In general all functions which evaluate an expression
Jost> (either direct or indirect) need an environment argument.
Jost> But also all gh_new_procedure* procedures (in gh_funcs).
From my perspective, the gh_new_procedure stuff is the only thing that
is likely to break many things. Would it be trivial to have
gh_new_procedure always add to the (guile-user) module (or something)
and then create a new function gh_add_procedure that takes a module
argument? Then gh_new_procedure could be deprecated.
The same idea could be applied to all the other changes, the old
version implicitly works on (guile-user) and the new improved version
handles the full blown glory of environments.
Thanks,
Clark