From: Mikael Djurfeldt <mdjurfeldt@gmail.com>
Cc: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Subject: Generalized vs generic
Date: Thu, 10 Feb 2005 10:58:41 +0100 [thread overview]
Message-ID: <66e540fe05021001586e652353@mail.gmail.com> (raw)
I've started to adapt my applications to the new vector and array interfaces.
To me, the name "generalized_vector" feels a bit odd and heavy.
Looking in the dictionaries, it seems like the term "generic_vector"
would be more fitting. What do the native English speakers say?
Should we use the names:
scm_is_generic_vector
scm_c_generic_vector_length
etc
instead of the current:
scm_is_generalized_vector
scm_c_generalized_vector_length
etc
?
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2005-02-10 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 9:58 Mikael Djurfeldt [this message]
2005-02-11 21:34 ` Generalized vs generic Kevin Ryde
2005-02-12 10:55 ` Mikael Djurfeldt
2005-02-20 23:14 ` Kevin Ryde
2005-02-28 2:02 ` Marius Vollmer
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=66e540fe05021001586e652353@mail.gmail.com \
--to=mdjurfeldt@gmail.com \
--cc=djurfeldt@nada.kth.se \
/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).