From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: list3i etc.
Date: Thu, 07 Mar 2013 11:23:12 +0200 [thread overview]
Message-ID: <834ngn1s3j.fsf@gnu.org> (raw)
In-Reply-To: <513856A1.1050408@yandex.ru>
> Date: Thu, 07 Mar 2013 12:58:09 +0400
> From: Dmitry Antipov <dmantipov@yandex.ru>
> CC: emacs-devel@gnu.org
>
> On 03/07/2013 11:01 AM, Eli Zaretskii wrote:
>
> >> Can we have a more mnemonically significant names for these, please?
> >> Like list_of_numbers2, list_of_numbers3, etc., for example?
>
> Of course we can. But IMHO they're "mnemonically significant" already,
Obviously, I disagree. The names list2, list3 etc. _are_ good for
mnemonics, because all they do is construct lists of N members. But
what is the 'i' part is completely obfuscated, IMO.
If the length of the name is a factor, then I can suggest list_ints2,
list_ints3 etc.
> and the similar approach is widely used here and there. For example,
> OpenGL API uses glFoo[sifd] to denote versions of glFoo with short/int/
> float/double arguments.
That others sin similarly shouldn't stop us from doing TRT ;-)
> > Also, why are they implemented as inline functions? They call list,
> > list3, etc. which aren't inlined.
>
> Hm... I guess that we don't want function call overhead for such a simple
> things
Why not? Are these used in any context where speed matters?
next prev parent reply other threads:[~2013-03-07 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 6:22 list3i etc Eli Zaretskii
2013-03-07 7:01 ` Eli Zaretskii
2013-03-07 8:58 ` Dmitry Antipov
2013-03-07 9:11 ` Xue Fuqiao
2013-03-07 9:30 ` Dmitry Antipov
2013-03-07 22:46 ` Stephen J. Turnbull
2013-03-07 9:23 ` Eli Zaretskii [this message]
2013-03-07 21:17 ` Paul Eggert
2013-03-09 1:59 ` Stefan Monnier
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834ngn1s3j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=emacs-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).