From: Dmitry Antipov <dmantipov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stephen@xemacs.org, Paul Eggert <eggert@cs.ucla.edu>,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: ptrdiff_t misuse
Date: Fri, 06 Jul 2012 20:42:28 +0400 [thread overview]
Message-ID: <4FF71574.5000207@yandex.ru> (raw)
In-Reply-To: <8339543mnf.fsf@gnu.org>
On 07/06/2012 08:00 PM, Eli Zaretskii wrote:
>> Yes, that's the point -- if ptrdiff_t and EMACS_POS
>> would span the same range of values, why bother to
>> distinguish the two?
>
> Because Emacs positions are not pointers, nor differences between
> pointers.
IMHO you mix the confusing type name and it's real use.
I read ptrdiff_t exactly as "difference between pointers", and this is
the minor drawback; the major one is that there is no standard unsigned
counterpart, like for size_t/ssize_t pair.
>> Whether a value is a buffer position is usually clearly stated in
>> the variable name.
>
> I refer you to the recent repeated confusions about this by Dmitry.
This isn't related to any type (mis)use. In a struct window,
window_end_pos really means something like last_displayed_pos;
this is quite hard to mix with window_end_[whatever].
Dmitry
next prev parent reply other threads:[~2012-07-06 16:42 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 [this message]
2012-07-06 17:39 ` Paul Eggert
2012-07-07 1:31 ` Chong Yidong
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=4FF71574.5000207@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stephen@xemacs.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).