This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: Trouble understanding define (!)
- To: mlivshin at bigfoot dot com
- Subject: Re: Trouble understanding define (!)
- From: Neil Jerram <neil at ossau dot uklinux dot net>
- Date: Fri, 4 Feb 2000 00:08:38 GMT
- CC: mdj at mdj dot nada dot kth dot se, guile at sourceware dot cygnus dot com
- References: <200001142054.UAA00622@ossau> <p2tzou4o5ov.fsf@pampelmuse.zrz.tu-berlin.de> <200001182250.WAA00624@ossau> <xy7ya9nezzz.fsf@mdj.nada.kth.se> <200001221200.MAA00478@ossau> <xy7bt6e82ru.fsf@mdj.nada.kth.se> <s3zotxrqoz.fsf@verisity.com> <xy7iu0cbc1z.fsf@mdj.nada.kth.se> <s3iu0bq1x5.fsf@verisity.com> <xy7bt63bxe3.fsf@mdj.nada.kth.se> <200001302033.UAA00458@ossau> <s37lgqdv97.fsf@verisity.com>
Michael Livshin writes:
why would you ever want to block your methods from extending an
imported generic? so you can have something like CL's `with-methods'
in a module scope? while this does seem possible, it hardly seems
useful.
Just to avoid spurious name conflicts. Suppose you import a module
that includes a generic function called "smith", but "smith" is not
the reason why you are importing the module. Then suppose that
"smith" also happens to be the most appropriate name for a generic
function that you want in your own application code.
one addition: defining a class slot with an
(#:accessor/#:setter/#:getter NAME) argument raises error if
(not (is-a? GF NAME)).
Good idea.
Regards,
Neil