From: "Mikael Djurfeldt" <mdjurfeldt@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: [goops] adding a number class with generic methods
Date: Thu, 4 May 2006 21:26:04 +0200 [thread overview]
Message-ID: <66e540fe0605041226q2a570820xc4eb08fc68051eb5@mail.gmail.com> (raw)
In-Reply-To: <IYR9E3$E5C0D83013B030AF134414D4507E68C7@poste.it>
On 5/4/06, Marco Maggi <marco.maggi-ipsu@poste.it> wrote:
> "Neil Jerram" wrote:
> >"Marco Maggi" <marco.maggi-ipsu@poste.it> writes:
> > "marco.maggi-ipsu@poste.it" wrote:
> >> I do not understand why the first solution does not work;
> >>I've tried different combinations of functions but there is
> >>something I am missing.
> >
> > Damn... it seems to work if I do not EXPORT the generic
> > methods.
> >
> >You mean if you remove the "(export =)" line?
>
> Yes, with the following and no EXPORT invocation
> it works.
Actually, logically this *is* how the code should be structured. If
you had created a novel generic function within your module, that
function should have been exported. But what you really want is just
to add methods to the pre-existing generic function = which you
(implicitly) *import* into your module.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-05-04 19:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 19:13 [goops] adding a number class with generic methods Marco Maggi
2006-05-04 19:26 ` Mikael Djurfeldt [this message]
2006-05-06 23:07 ` Neil Jerram
2006-05-07 9:37 ` Mikael Djurfeldt
2006-05-07 11:45 ` Neil Jerram
2006-05-09 7:56 ` Ludovic Courtès
2006-05-09 8:30 ` Mikael Djurfeldt
2006-05-09 9:43 ` GOOPS and Code Complexity Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2006-05-03 5:36 [goops] adding a number class with generic methods Marco Maggi
2006-05-04 7:47 ` Neil Jerram
2006-05-02 20:16 Marco Maggi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=66e540fe0605041226q2a570820xc4eb08fc68051eb5@mail.gmail.com \
--to=mdjurfeldt@gmail.com \
--cc=djurfeldt@nada.kth.se \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).