delorie.com/archives/browse.cgi | search |
Date: | Wed, 12 May 1999 17:19:21 +0300 (EET DST) |
From: | Eugene Ageenko <ageson AT cs DOT joensuu DOT fi> |
To: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
cc: | djgpp AT delorie DOT com, Pasi Franti <franti AT cs DOT joensuu DOT fi> |
Subject: | Re: Portability and size_t type related question |
In-Reply-To: | <Pine.SUN.3.91.990512170330.17607E-100000@is> |
Message-ID: | <Pine.SOL.4.10.9905121713580.9519-100000@cs.joensuu.fi> |
MIME-Version: | 1.0 |
Reply-To: | djgpp AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> > Q2. More complicated question: the type 'size_t'. > > Why is this a different question? The answer is the same as Q1. > Ok. thanx. it is like here then: typedef unsigned short U16; typedef unsigned long U32; typedef unsigned char BYTE; then I have to care when dealing with size_t type variables. I should cast type conversion in memory operation. I better eliminate all size_t variable type definitions, and change them to custom type as above, when using fucntions required size_t type I better use type conversion. Eugene
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |