caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ville-Pertti Keinonen <will@exomi.com>
To: skaller <skaller@users.sourceforge.net>
Cc: Niall Dalton <niall@xrnd.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Re: 64 bit windows
Date: Thu, 08 Sep 2005 10:50:29 +0300	[thread overview]
Message-ID: <1126165829.732.27.camel@acerf.exomi.com> (raw)
In-Reply-To: <1126126291.28300.13.camel@rosella.wigram>

On Thu, 2005-09-08 at 06:51 +1000, skaller wrote:

> Actually MS decision is vastly more sensible than the gnu choice:

It's not a GNU choice, it's what almost every vendor of 64-bit systems
has used for more than a decade.

It's nice to have a standard integer type for 64-bit values; C99 still
isn't sufficiently established and C++ has no suitable standard types
other than long.

The Microsoft decision is only sensible in the context where Microsoft
makes their decisions (only Windows matters, incompatibility with the
rest of the world is good).

> The real 'gotcha' is the Unix programmers that decided
> it was OK to use 32 bit ints as addresses .. their code
> will break under both models.

It's also sometimes necessary to represent pointers as integers.  I've
seen more code that uses long for this purpose than int, often with
assertions to ensure that sizeof(long) == sizeof(void *).

All of my Unix C code works just by recompiling for amd64.  On an LLP64
system, many things would break (garbage collectors and such where
representing pointers as integers is necessary).

Personally, I'm very happy that DEC, SGI, Sun, IBM, HP and Apple have
all went with LP64.



      reply	other threads:[~2005-09-08  7:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 15:31 64 windows caml Niall Dalton
2005-09-07 14:36 ` 64 bit windows Niall Dalton
2005-09-07 20:51   ` [Caml-list] " skaller
2005-09-08  7:50     ` Ville-Pertti Keinonen [this message]

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=1126165829.732.27.camel@acerf.exomi.com \
    --to=will@exomi.com \
    --cc=caml-list@inria.fr \
    --cc=niall@xrnd.com \
    --cc=skaller@users.sourceforge.net \
    /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 NNTP newsgroup(s).