unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
Subject: where to put generics?
Date: Sat, 12 Jul 2003 11:30:36 +0100	[thread overview]
Message-ID: <20030712103036.GB4329@lark> (raw)

Hi again,

I figured while I was emailing I could get something else off my chest
-- what is the best way for two modules that do not want to know about
each other to add methods to the same generic? The problem there is that
such a generic might not exist in the 'stock' top-level environment. The
generic would need to be created and then exported, but only one time --
if both modules export generics, the generics from recent modules will
replace those from previous modules.

So, if the generics are only exported once, where should they be put?
I'm hacking around this for the moment by putting them in the root
module, but that's not exactly an elegant solution. What's the thought
on this? Has anyone else had to deal with these issues in the past?

Thanks again,

wingo.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


             reply	other threads:[~2003-07-12 10:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12 10:30 Andy Wingo [this message]
2003-07-14 16:42 ` where to put generics? Mikael Djurfeldt

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=20030712103036.GB4329@lark \
    --to=wingo@pobox.com \
    /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).