X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	"Dave Bloodgood" <dabldgd AT cox DOT net>
Newsgroups:	comp.os.msdos.djgpp
References:	<baec0bf0 DOT 0403012323 DOT 10896c3 AT posting DOT google DOT com> <esd840d8dde7matafu4vd11bsvagshadkl AT 4ax DOT com> <baec0bf0 DOT 0403020529 DOT 8f42598 AT posting DOT google DOT com>
Subject:	Re: 16 bit integers
Lines:	19
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID:	<Xk01c.25898$aZ3.23018@fed1read04>
Date:	Tue, 2 Mar 2004 05:55:02 -0800
NNTP-Posting-Host:	68.4.28.212
X-Complaints-To:	abuse AT cox DOT net
X-Trace:	fed1read04 1078235575 68.4.28.212 (Tue, 02 Mar 2004 08:52:55 EST)
NNTP-Posting-Date:	Tue, 02 Mar 2004 08:52:55 EST
Organization:	Cox Communications
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Use "short"'s instead of Int ( which are really long ). They can be signed
or unsigned, and are guaranteed
to be 16 bits

Dave
"Andrey" <huli_ebtyt AT list DOT ru> wrote in message
news:baec0bf0 DOT 0403020529 DOT 8f42598 AT posting DOT google DOT com...
> And what if I want to process an array of 16-bit data loaded from a file,
> should I use?:
>
> a = *(pointer)&0x0000ffff;
> b = *(pointer)>>16;
> ...
> work with a, b
> ...
>
> I think it is not optimal...

- Raw text -