Re: generic methods and trailing arguments
"Lars J. Aas" [EMAIL PROTECTED] writes: With Goops' generic methods, it seems like trailing arguments are ignored when method arbitration is done. Take for instance this example: (define-method (hello arg) (display "1 arg\n")) (define-method (hello arg arg2) (display "2 args\n")) (hello 1) = 1 arg (hello 1 2) = 2 args (hello 1 2 3) = 2 args Is there a way to make the method arbitration more strict? Maybe it's a bug? It's a bug. ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: generic methods and trailing arguments
"Lars J. Aas" [EMAIL PROTECTED] writes: With Goops' generic methods, it seems like trailing arguments are ignored when method arbitration is done. Take for instance this example: (define-method (hello arg) (display "1 arg\n")) (define-method (hello arg arg2) (display "2 args\n")) (hello 1) = 1 arg (hello 1 2) = 2 args (hello 1 2 3) = 2 args Is there a way to make the method arbitration more strict? Maybe it's a bug? It's a bug. ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: generic methods and trailing arguments
Mikael Djurfeldt [EMAIL PROTECTED] writes: "Lars J. Aas" [EMAIL PROTECTED] writes: With Goops' generic methods, it seems like trailing arguments are ignored when method arbitration is done. Take for instance this example: (define-method (hello arg) (display "1 arg\n")) (define-method (hello arg arg2) (display "2 args\n")) (hello 1) = 1 arg (hello 1 2) = 2 args (hello 1 2 3) = 2 args Is there a way to make the method arbitration more strict? Maybe it's a bug? It's a bug. The bug should be fixed now in the CVS version of guile-core. If/when I make an independent release of GOOPS, the bugfix will be included there as well. Thanks, Mikael ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
