From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: Generalized vs generic
Date: Mon, 28 Feb 2005 03:02:09 +0100 [thread overview]
Message-ID: <87d5ulfnmm.fsf@zagadka.de> (raw)
In-Reply-To: <87ekfaq0xg.fsf@zip.com.au> (Kevin Ryde's message of "Mon, 21 Feb 2005 10:14:19 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Mikael Djurfeldt <mdjurfeldt@gmail.com> writes:
>>
>> Well, to me that specific meaning---a function that can operate on any
>> of a set of types---is just another example of what we have here: a
>> vector that can be any of a set of types, so my view is that its just
>> an advantage to use the same term.
>
> Sounds fair.
I am fine with changing "generalized" to "generic" as well. Mikael,
please go ahead, if you want to.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2005-02-28 2:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 9:58 Generalized vs generic Mikael Djurfeldt
2005-02-11 21:34 ` Kevin Ryde
2005-02-12 10:55 ` Mikael Djurfeldt
2005-02-20 23:14 ` Kevin Ryde
2005-02-28 2:02 ` Marius Vollmer [this message]
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=87d5ulfnmm.fsf@zagadka.de \
--to=mvo@zagadka.de \
--cc=guile-devel@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).