From: Endlisnis <s257m AT unb DOT ca>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: as internal declarations - gfx demo
Date: Sun, 30 Aug 1998 11:51:07 -0300
Organization: NBTel Internet
Lines: 17
Message-ID: <35E966DB.6B6C260A@unb.ca>
References: <E0zCSn7-0005A4-00 AT sable DOT ox DOT ac DOT uk> <35E87E2E DOT 7D5D AT geocities DOT com>
NNTP-Posting-Host: fctnts12c40.nbnet.nb.ca
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Adam Brown wrote:
> > "long" is at least as wide as "int", which is at least as wide as
> > "short".  In addition, "short" is at least 16 bits wide and "long" is
> > at least 32 bits wide.
> >
> >     16 bits  <=  short  <=  int  <=  long  >=  32 bits
	So how come 'long' was not set to 64-bits?  Wouldn't that have made it easier
to use 64-bit variables without being totally ANSI un-complient?  Why make up
'long long's when 'long's have been wasted?  I suppose this has to do with
UNIX compatability.  It just seems odd to have 'int' the same as 'long'.
-- 
     (\/) Endlisnis (\/)
          s257m AT unb DOT ca
          Endlisnis AT GeoCities DOT com
          Endlis AT nbnet DOT nb DOT ca