delorie.com/archives/browse.cgi | search |
Date: | Thu, 18 May 2000 11:33:47 +0300 (IDT) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | "Alexei A. Frounze" <alex DOT fru AT mtu-net DOT ru> |
cc: | djgpp AT delorie DOT com |
Subject: | Re: C++, complex, etc |
In-Reply-To: | <39236A55.78749ABD@mtu-net.ru> |
Message-ID: | <Pine.SUN.3.91.1000518113101.12245I-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Thu, 18 May 2000, Alexei A. Frounze wrote: > I don't use size_t in my sources. You cannot do that if those sources call standard functions which accept or return size_t values, such as strlen, memcpy, malloc, etc. If you use int instead of size_t in these cases, your code becomes non-portable. > Only standard types: char, short, int, long int, long long,... size_t is a standard type, it is defined by the ANSI/ISO C standard (the old one, known as C90).
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |