[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange interaction of define-method with the module system
From: |
Mikael Djurfeldt |
Subject: |
Re: Strange interaction of define-method with the module system |
Date: |
30 Nov 2000 19:50:42 +0100 |
User-agent: |
Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 |
Matthias Koeppe <address@hidden> writes:
> I am trying to define an exported method FOO in the previously defined
> module MURKS using the code below. The defined method will not be
> visible in GUILE-USER although it uses the MURKS module. Note that the
> symbol FOO naming the method is not unbound (it seeems to get bound to
> #f in the GUILE-USER module).
>
> (I need this for making Guile work with ILISP, a generalized Emacs
> interface to Lisp systems.)
>
> (define-module (murks)
> :use-module (oop goops))
>
> (define-module (guile-user)
> :use-module (oop goops)
> :use-module (murks))
>
> (eval '(define-method foo ((a <integer>)) a) (resolve-module '(murks)))
> (eval '(export foo) (resolve-module '(murks)))
>
> (foo 1) ; ==> ERROR: Wrong type to apply: #f
This is not a result of interaction between define-method and the
module system. It is a result of the module system only.
Unfortunately, I don't have time to help you find the bug, but I
should say that both the module system and the export form will be
replaced. Maybe someone else can help?