www.delorie.com/archives/browse.cgi | search |
From: | Eugene Ageenko <ageson AT cs DOT joensuu DOT fi> |
Newsgroups: | comp.os.msdos.djgpp,gnu.gcc,gnu.gcc.help |
Subject: | Re: Portability and size_t type related question |
Date: | Thu, 13 May 1999 13:12:00 +0300 |
Organization: | University of Joensuu / Dept. of Computer Sci. |
Lines: | 18 |
Message-ID: | <373AA570.E2AF141B@cs.joensuu.fi> |
References: | <Pine DOT SOL DOT 4 DOT 10 DOT 9905121713580 DOT 9519-100000 AT cs DOT joensuu DOT fi> |
NNTP-Posting-Host: | cspc52.joensuu.fi |
Mime-Version: | 1.0 |
X-Mailer: | Mozilla 4.51 [en] (Win95; I) |
X-Accept-Language: | ru |
CC: | Pasi Franti <franti AT cs DOT joensuu DOT fi>, |
Juha Hakkarainen <jhakka AT cs DOT joensuu DOT fi> | |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Thank you all for the answer. When I need to get portable i/o I will read/write by byte chunks When I need memory variable to be exactly 32-bit long, I will define type for it (like U32), and then change this type depending on the system. I understand that this case is not a bets solution, and one better to avoid it, but it is indeed important in a low level operations (e.g. ari-coder) I think it is the way it is. Eugene
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |