Date: Thu, 13 May 1999 16:14:06 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Shawn Hargreaves <ShawnH AT Probe DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: Portability and size_t type related question
In-Reply-To: <8D53104ECD0CD211AF4000A0C9D60AE301397599@probe-2.acclaim-euro.net>
Message-ID: <Pine.SUN.3.91.990513161217.12629S-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 13 May 1999, Shawn Hargreaves wrote:

> As long as you make some minimal assumptions (eg. 
> that you can fit at least 32 bits in an int, or assume at least 16 
> bits if you want to support 16 platforms as well), and don't rely 
> on any specific wrapping behaviour, I've never found a case where
> I really needed this kind of define.

You might need that if you have to refer to the maximum value that a 
given data type can hold.

Of course, as long as you can do without depending on specific data 
types, you should do that.