From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-user@gnu.org
Subject: Re: Do we have to worry about the names of generic functions?
Date: Thu, 13 May 2004 12:53:24 -0500 [thread overview]
Message-ID: <87n04ctdrf.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87wu3h2xli.fsf@ivanova.rotty.yi.org> (Andreas Rottmann's message of "Wed, 12 May 2004 22:34:49 +0200")
Andreas Rottmann <a.rottmann@gmx.at> writes:
> Yes, but when the non-generic are procedures, you can "upgrade" them:
>
> (define quit (ensure-generic quit))
Hmm, but since you really don't know about all the other modules out
there, it seems like the safest thing when using really general names
might be to do this for all of your exported generics. Although that
feels a bit crufty, and I presume still doesn't protect you from
exports that aren't a procedure or a method.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-05-13 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 10:34 Do we have to worry about the names of generic functions? Andy Wingo
2004-05-12 16:14 ` Paul Jarc
2004-05-12 20:34 ` Andreas Rottmann
2004-05-13 17:53 ` Rob Browning [this message]
2004-05-13 18:08 ` Andreas Rottmann
2004-05-13 19:49 ` Rob Browning
2004-05-14 19:40 ` Andy Wingo
2004-05-15 19:53 ` Paul Jarc
2004-05-13 18:38 ` Rob Browning
2004-05-14 19:53 ` Andy Wingo
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=87n04ctdrf.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).