cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/1997/08/30/06:04:10

From: Charles Krug <charles AT pentek DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Why does sizeof give me...
Date: Thu, 28 Aug 1997 08:40:10 +0100
Lines: 25
Message-ID: <34052B5A.2F5D@pentek.com>
References: <97Aug13.151644gmt+0100 DOT 17061 AT internet01 DOT amc DOT de> <33F68612 DOT 5EF83660 AT alcyone DOT com>
NNTP-Posting-Host: mail.pentek.com
Mime-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Erik Max Francis wrote:
> 
> Chris Croughton wrote:
> 
> > I have used one compiler (VAX, possibly?) which had short = int = long
> > and
> > all 32 bit.
> 

Under TIs compiler for their C3x and C4x DSPs, ALL data is 32-bits
wide--including characters.

> 
> I don't know offhand, but my understanding is that ANSI C doesn't make any
> determination of the internal respresentation of the bytes in a multi-byte
> integral type (short, int, long).  I imagine that there aren't any such
> arbitrary architectures that aren't either little- or big-endian.
> 

Most C compilers, including djgpp, come with the file limits.h, which
defines macros for the value limits for every native data type. 
#include'ing it will give you the information you need

-- 
Charles Krug, Jr.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019