From: Chong Yidong <cyd@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
dmantipov@yandex.ru, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: ptrdiff_t misuse
Date: Sat, 07 Jul 2012 09:31:27 +0800 [thread overview]
Message-ID: <87r4sofjbk.fsf@gnu.org> (raw)
In-Reply-To: <83ipe12s6r.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Jul 2012 11:46:04 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> If this is indeed the reason, I suggest a new typedef:
>
> typedef ptrdiff_t EMACS_POS;
>
> to be used with all such variables. I think this will contribute to
> clarity of the code, since ptrdiff_t is a rarely-used type, and thus I
> expect many programmers to be unfamiliar with it. By contrast,
> EMACS_POS by its very name tells what the variable can and cannot
> hold.
This is a bad idea. Since EMACS_POS would occur rarely in the code, it
would be necessary to look up what it means when you stumble across it.
It would be easier to simply remember the meaning and use of ptrdiff_t.
Introducing yet another type defeats the purpose.
next prev parent reply other threads:[~2012-07-07 1:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 13:20 (unknown) Eli Zaretskii
2012-06-29 14:18 ` ptrdiff_t misuse [was :Re: (empty)] Dmitry Antipov
2012-06-29 17:07 ` Stefan Monnier
2012-06-30 7:13 ` Paul Eggert
2012-06-30 7:27 ` Eli Zaretskii
2012-06-30 13:12 ` Paul Eggert
2012-06-30 14:23 ` Stefan Monnier
2012-06-30 12:07 ` Stefan Monnier
2012-06-30 13:14 ` Paul Eggert
2012-06-30 14:23 ` Stefan Monnier
2012-07-04 6:25 ` Paul Eggert
2012-07-04 16:39 ` Eli Zaretskii
2012-07-04 18:19 ` Paul Eggert
2012-07-05 16:31 ` Eli Zaretskii
2012-07-05 19:34 ` Eli Zaretskii
2012-07-06 0:08 ` Paul Eggert
2012-07-06 6:43 ` Eli Zaretskii
2012-07-06 7:32 ` Paul Eggert
2012-07-06 8:34 ` ptrdiff_t misuse Eli Zaretskii
2012-07-06 14:51 ` Paul Eggert
2012-07-06 21:30 ` Stefan Monnier
2012-07-06 21:33 ` Samuel Bronson
2012-07-07 10:59 ` Stefan Monnier
2012-07-07 15:34 ` Paul Eggert
2012-07-06 8:46 ` Eli Zaretskii
2012-07-06 10:19 ` Stephen J. Turnbull
2012-07-06 11:01 ` Eli Zaretskii
2012-07-06 12:02 ` Stephen J. Turnbull
2012-07-06 13:37 ` Eli Zaretskii
2012-07-06 16:25 ` Stephen J. Turnbull
2012-07-06 14:56 ` Paul Eggert
2012-07-06 15:43 ` Eli Zaretskii
2012-07-06 15:56 ` Paul Eggert
2012-07-06 16:00 ` Eli Zaretskii
2012-07-06 16:42 ` Dmitry Antipov
2012-07-06 17:39 ` Paul Eggert
2012-07-07 1:31 ` Chong Yidong [this message]
2012-06-29 18:54 ` ptrdiff_t misuse [was :Re: (empty)] Eli Zaretskii
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=87r4sofjbk.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).