From: Robert.Cross@scottish-newcastle.co.uk
To: gnu-win32@cygnus.com
Subject: Re: long long vs long
Date: Fri, 24 Jul 1998 05:20:00 -0000 [thread overview]
Message-ID: <01IZRUQKGPIE0003P4@scottish-newcastle.co.uk> (raw)
nleroy@norland.com wrote:
#Technically, it doesn't make sense, at least in the PC world, where
#all processors are <=32bits.
PICKY_MODE = TRUE
surely not *all* PC processors - what about the Alpha's? I realise that
they're not really widespread, but they are out there. I suppose you could
also count PowerPC in that vein.
PICKY_MODE = FALSE
#Probably the more pervasive reason, however, is that there exists A
#LOT of code out there which expects sizeof(long)==4. It's sort-of an
#un-official C standard. In particular, legacy code dealing with
#networking, etc., is frequently very loaded with such assumptions.
#IIRC, the original CRAY C compiler used a 32-bit long and a 64-bit
#int, just because so much code had this expectation.
Yes, and just to confuse the issue, the later compilers used 48bit as the
default. Although you could say '-i64' on the command line to promote these
variables
all to 64bit.
#IMHO: C should have included standard data sizes, as well as it's generic
types. It
#would have made many things a lot simpler.
Agreed. Personally I cannot see a problem with :
short = 8bits, int=16bits, long=32bits, (long long = 64 bits)
other than possible problems when Merced et al are around, rumour has it that
this
is 128bit native? So what would this be - "long long long" perhaps?
Bob Cross.
next reply other threads:[~1998-07-24 5:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-24 5:20 Robert.Cross [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-08-04 16:53 dahms
1998-08-01 2:01 Joerg Pommnitz
1998-07-29 16:23 dahms
1998-07-27 18:55 dahms
1998-07-24 12:58 Earnie Boyd
1998-07-23 11:42 Martin Portmann
1998-07-23 11:42 sjm
1998-07-22 17:12 John Estabrook
1998-07-22 10:06 Earnie Boyd
1998-07-23 0:43 ` $Bill Luebkert
1998-07-21 1:55 Graham Murray
1998-07-22 6:17 ` Harry Broomhall
1998-07-22 13:57 ` Michael H. Warfield
1998-07-23 6:15 ` Harry Broomhall
1998-07-23 13:02 ` Matthew Donadio
1998-07-23 15:30 ` Timothy Writer
1998-07-24 12:58 ` Matthew Donadio
1998-07-25 0:08 ` Larry Hall
1998-07-25 1:22 ` Timothy Writer
1998-07-24 12:58 ` Benjamin Riefenstahl
1998-07-22 13:57 ` Nicholas R LeRoy
1998-07-22 16:50 ` Michael Weiser
1998-07-23 8:33 ` Harry Broomhall
1998-07-23 19:01 ` Michael Weiser
1998-07-24 5:20 ` Harry Broomhall
1998-07-25 0:08 ` Mumit Khan
1998-07-26 9:27 ` sjm
[not found] ` <9807261625.AA18550.cygnus.gnu-win32@frodo>
1998-07-28 0:57 ` Christopher G. Faylor
1998-07-27 14:23 ` Michael Weiser
1998-07-25 1:22 ` Timothy Writer
1998-07-28 0:57 ` Michael Weiser
1998-07-24 0:25 ` massimo morara
1998-07-23 8:33 ` Brian Osman
1998-07-27 14:23 ` Michael Weiser
1998-07-22 17:12 ` Andrew Sharp
[not found] <Michael>
[not found] ` <H.>
[not found] ` <Warfield"'s>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Wed,>
[not found] ` <22>
[not found] ` <Jul>
[not found] ` <1998>
[not found] ` <11:08:42>
[not found] ` <-0400>
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=01IZRUQKGPIE0003P4@scottish-newcastle.co.uk \
--to=robert.cross@scottish-newcastle.co.uk \
--cc=gnu-win32@cygnus.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.
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).