delorie.com/archives/browse.cgi | search |
Date: | Mon, 22 May 2000 09:35:55 +0300 (IDT) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | djgpp AT delorie DOT com |
Subject: | Re: C++, complex, etc |
In-Reply-To: | <uvneis0fs5pf6p6ea8b2icsthfb429q5rb@4ax.com> |
Message-ID: | <Pine.SUN.3.91.1000522093504.22890I-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 Mon, 22 May 2000, Damian Yerrick wrote: > >sizeof doesn't help here: it cannot tell whether size_t is signed or > >unsigned. > > But reading the standard ("size_t is unsigned") can. You are taking my message out of context. The context was how does an ANSI C program do that automatically (to stay portable). I have yet to see a program that can read the ANSI C spec at compile time.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |