This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: Trouble understanding define (!)
- To: clark dot mcgrew at sunysb dot edu
- Subject: Re: Trouble understanding define (!)
- From: Mikael Djurfeldt <mdj at mdj dot nada dot kth dot se>
- Date: 22 Jan 2000 09:03:55 +0100
- Cc: neil at ossau dot uklinux dot net, jostobfe at calvados dot zrz dot TU-Berlin dot DE, guile at sourceware dot cygnus dot com, djurfeldt at nada dot kth dot se
- Cc: djurfeldt at nada dot kth dot se
- References: <200001142054.UAA00622@ossau> <p2tzou4o5ov.fsf@pampelmuse.zrz.tu-berlin.de> <200001182250.WAA00624@ossau> <xy7ya9nezzz.fsf@mdj.nada.kth.se> <m12BoPI-000UugC@ale.physics.sunysb.edu>
Clark McGrew <mcgrew@ale.physics.sunysb.edu> writes:
> >>>>> "Mikael" == Mikael Djurfeldt <mdj@mdj.nada.kth.se> writes:
>
> Mikael> * importing generics from another module (should one
> Mikael> binding of a generic shadow another with the same name, or
> Mikael> should the module system create a new generic function,
> Mikael> containing a union of the methods; I actually begin to
> Mikael> favor the latter alternative)
>
> An emphatic yes please for the latter... Otherwise it's going to be
> hard and have common generics like "print" work as expected when
> several different modules of classes are imported.
Hmm... otherwise, one can of course regard one of the modules as
having the "main" reposibility for `print'. E.g., `print' is really
`display' or `write' in the R5RS module (currently, the root module
(guile)). Anyone using this module, won't have problems if the user
of `display' uses the same module (it is of course also OK to export
it from your module, as long as you don't create `display' by
yourself).