Re: new module directive?

[Andreas Rottmann]

"Michael Burschik" <address@hidden> writes:

> Andreas Rottmann says:
>
>> The hairy thing is when you want to override (extend) a non-generic
>> with a generic. #:re-export won't work in this case and #:export gives
>> a warning.
>
> This is pretty nasty, especially since #:re-export gives no indication of
> not working, and I did not, in fact, notice that it does not. I extended
> equal? with a generic and it seemed to work as expected when I used
> #:re-export. Was this simply a coincidence, or is equal? generic anyway?
>
As soon GOOPS is loaded, equal? is changed to a
"primitive-generic". IMHO, it would be nice if that would happen for
every procedure...

guile> equal?
#<primitive-procedure equal?>
guile> (use-modules (oop goops))
guile> equal?
#<primitive-generic equal?>

Andy
-- 
Andreas Rottmann         | address@hidden      | address@hidden | address@hidden
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

Make free software, not war!