public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Martin Portmann <map@graph-tech.ch>
To: gnu-win32@cygnus.com
Subject: RE: long long vs long
Date: Thu, 23 Jul 1998 11:42:00 -0000	[thread overview]
Message-ID: <FDF94A49B791D011951E0000C07E6DED091ABC@srv-nt-1.graph-tech.ch> (raw)

   That's why portable code use some typedefs that will be 
   redefined according to the CPU/OS.

   -----------------------------------------------------
   Martin Portmann               Mobile +41 79 330 60 12
   Software Department            Phone +41 62 896 42 40 
   Graph-Tech AG, Switzerland          map@graph-tech.ch
            http://www.graph-tech.ch/english/people/map/



> -----Original Message-----
> From:	michael@weiser.saale-net.de [SMTP:michael@weiser.saale-net.de]
> Sent:	Wednesday, July 22, 1998 9:20 PM
> To:	gnu-win32@cygnus.com
> Subject:	Re: long long vs long
> 
> Hi Graham,
> 
> You wrote:
> 
> >This is probably a silly question, but rather than having long long
> for
> >64 bit, why was long not made 64bit? The standard (AFAIK) states that
> >short <= int <= long.  So, it should be possible for long to be 64
> bit
> >rather than 32. This would give a simple progression from 8bit chars
> to
> >64bit longs.
> No because the standard says
> short == 16 bit
> long  == 32 bit
> int   == 16 or 32 depending on the machine's architecture
> 
> For example: Under DOS int is 16 bit while under Win32 und UN*X it is
> 32 bit.
> So there's no way for long to be 64 bit while conforming to the
> standard.
> 
> bye
> 
> Michael
> -
> For help on using this list (especially unsubscribing), send a message
> to
> "gnu-win32-request@cygnus.com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1998-07-23 11:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-23 11:42 Martin Portmann [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-24  5:20 Robert.Cross
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 ` Nicholas R LeRoy
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 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=FDF94A49B791D011951E0000C07E6DED091ABC@srv-nt-1.graph-tech.ch \
    --to=map@graph-tech.ch \
    --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).