From: Eugene Ageenko <ageson AT cs DOT joensuu DOT fi>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Portability and size_t type related question
Date: Thu, 13 May 1999 13:15:13 +0300
Organization: University of Joensuu / Dept. of Computer Sci.
Lines: 25
Message-ID: <373AA630.485A105A@cs.joensuu.fi>
References: <Pine DOT SOL DOT 4 DOT 10 DOT 9905130944050 DOT 5527-100000 AT cs DOT joensuu DOT fi>
NNTP-Posting-Host: cspc52.joensuu.fi
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.51 [en] (Win95; I)
X-Accept-Language: ru
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com



Pasi Franti wrote:
> 
> > Ok. thanx. it is like here then:
> >
> > typedef  unsigned short    U16;
> > typedef  unsigned long     U32;
> > typedef  unsigned char     BYTE;
> 
> I disagree.
> 
> I did not follow your discussion but how did you come up to such
>

exactly.

I have said that I have defined new types in our software (like it is
done in some modules already. see coder source code for example)

the definitions now in a one place and it is easy to find them and
change in a different system.
No wonder I come to problem, if was pushed to use standard types. ;)

Eugene