all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Helmut Eller <eller.helmut@gmail.com>, 5114@emacsbugs.donarmstrong.com
Subject: bug#5114: 23.1.50; (string-to-number (number-to-string most-positive-fixnum))
Date: Sat, 05 Dec 2009 18:44:42 +0200	[thread overview]
Message-ID: <83aaxxjrph.fsf@gnu.org> (raw)
In-Reply-To: <m2ocmdjvpm.fsf@gmail.com>

> From: Helmut Eller <eller.helmut@gmail.com>
> Date: Sat, 05 Dec 2009 16:18:13 +0100
> Cc: 
> 
> * Eli Zaretskii [2009-12-05 15:25+0100] writes:
> 
> >> From: Helmut Eller <eller.helmut@gmail.com>
> >> Date: Sat, 05 Dec 2009 13:36:41 +0100
> >> Cc: 5114@emacsbugs.donarmstrong.com
> >> 
> >> +  else {
> >> +    unsigned long u = 0;
> >
> > This assumes that `unsigned long' is the same width as EMACS_INT.
> > This could be false, e.g., with 64-bit MS-Windows.  Isn't it better to
> > use EMACS_INT instead?
> 
> Using EMACS_UINT wouldn't hurt.  Does MOST_POSITIVE_FIXNUM not fit in a
> unsigned long on Windows?

In the 32-bit Windows build, it does.  In the 64-bit Windows build
(which does not yet exist, since we don't yet support it), it will
not, because MS in their infinite wisdom (probably because backward
compatibility considerations wrt existing source code and headers)
decided to use the LLP64 programming model.

> I assumed that longs are supposed to be as wide as pointers.

Not on 64-bit Windows, they don't.





  reply	other threads:[~2009-12-05 16:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 14:36 bug#5114: 23.1.50; (string-to-number (number-to-string most-positive-fixnum)) Helmut Eller
2009-12-03 20:52 ` Stefan Monnier
2009-12-05 12:36   ` Helmut Eller
2009-12-05 14:25     ` Eli Zaretskii
2009-12-05 15:18       ` Helmut Eller
2009-12-05 16:44         ` Eli Zaretskii [this message]
2011-09-18  9:47 ` Lars Magne Ingebrigtsen
2011-09-18 10:57   ` Leo

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83aaxxjrph.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=5114@emacsbugs.donarmstrong.com \
    --cc=eller.helmut@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.