From: Earnie Boyd <earnie_boyd@yahoo.com>
To: gw32 <gnu-win32@cygnus.com>, sjm <smorris@xionics.com>
Subject: Re: long long vs long
Date: Fri, 24 Jul 1998 12:58:00 -0000 [thread overview]
Message-ID: <19980724131448.5767.rocketmail@send101.yahoomail.com> (raw)
---sjm wrote:
>
>
> Earnie Boyd writes:
> > Or why not set a new standard something like
> >
> > int8, int16, int32, int64 to indicate the number of bits.
>
> Right! The ambiguity of variable sizes has been the most unportable
feature of
> C. I know why they did it but it is still a pain. In those days the
world
> hadn't decided whether word sizes would be a multiple of 6 or 8 bits.
> Implementing a 32 bit data type on an 18 bit (or 24 bit) machine
would have
> been a disaster. Some machines would have wanted int6, int12, int18
and int24
> as bacic integer sizes. It was better to leave word sizes ambiguous
and accept
> the portability problem.
>
If the compiler were to recognize the number following the `int' as
the number of bits to be used then one could specify whatever they
wished. This would lend itself to `no problem' when porting assuming
the compiler could recognize this format.
BTW, IMHO, short should be the sizeof(int)/2 and long should be
sizeof(int)*2.
==
- \\||//
---o0O0--Earnie--0O0o----
--earnie_boyd@yahoo.com--
------ooo0O--O0ooo-------
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1998-07-24 12:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-24 12:58 Earnie Boyd [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 5:20 Robert.Cross
1998-07-23 11:42 sjm
1998-07-23 11:42 Martin Portmann
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 ` Brian Osman
1998-07-27 14:23 ` 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-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=19980724131448.5767.rocketmail@send101.yahoomail.com \
--to=earnie_boyd@yahoo.com \
--cc=gnu-win32@cygnus.com \
--cc=smorris@xionics.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).