🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.std.c
Article #3776

Re: Why "long long" doesn't work.

#3776
From: halasz
Date: Fri, 18 Aug 1995 16:16
17 lines
1422 bytes
In article <1995Aug17.002758.15662@dcs.warwick.ac.uk>, A.Main@dcs.warwick.ac.uk (Zefram) writes
:  ....
: I think exact semantics are used sufficiently that language support is
: warranted.  At the moment, there is a great deal of code that assumes
: that int (or sometimes long) is exactly 32 bits, and that short is
: exactly 16 bits.  Much code relies on variables declared as unsigned
: int having a range of 0 to 0xffffffff.  If no form of exact
: specification is provided, people *will* write code that relies on int
: :64 (or int atleast:64) having exactly 64 bits (which it will in most
: implementations).  The SBEIR paper explains the need for the exact:
: specification quite well.

I suspect that all theze exact lengths are there becauz the lengths are
exact:  that is, a 32-bit-long 'int' is declared becauz the programmer wants
all the bits that the processor has.  In concluzion, I suspect that the
exact lengths are a matter of inquirie: I wish this manie, I get houmanie
for my wish?
Technical Details
Message-ID: <412ec1$dt0@caip.rutgers.edu>
Path: arc1-ca.pugleaf.net!caip.rutgers.edu!not-for-mail
References: <3v9s4l$9t5@caip.rutgers.edu> <3vk874$e0q@caip.rutgers.edu> <1995Aug17.002758.15662@dcs.warwick.ac.uk>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!caip.rutgers.edu!not-for-mail
From: halasz@caip.rutgers.edu
Newsgroups: comp.std.c
Subject: Re: Why "long long" doesn't work.
Date: 18 Aug 1995 12:16:01 -0400
Organization: Rutgers University
Message-ID: <412ec1$dt0@caip.rutgers.edu>
References: <3v9s4l$9t5@caip.rutgers.edu> <3vk874$e0q@caip.rutgers.edu> <1995Aug17.002758.15662@dcs.warwick.ac.uk>
NNTP-Posting-Host: caip.rutgers.edu