This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: Trouble understanding define (!)
- To: mdj at mdj dot nada dot kth dot se
- Subject: Re: Trouble understanding define (!)
- From: Neil Jerram <neil at ossau dot uklinux dot net>
- Date: Sat, 22 Jan 2000 12:00:00 GMT
- CC: jostobfe at calvados dot zrz dot TU-Berlin dot DE, guile at sourceware dot cygnus dot com, 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>
* importing generics from another module (should one binding of a
generic shadow another with the same name, or should the module
system create a new generic function, containing a union of the
methods; I actually begin to favor the latter alternative)
Unfortunately I think we have to do the latter. Otherwise we have a
situation where two unrelated applications (but in the same Guile
process) can interfere with each other by adding methods to the same
generic function imported from another module.
The problem is, what depth of copying do we need from the old generic
function to the new one? Is it enough to copy the methods by
reference, or do they need to be duplicated as well?
Neil