delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/08/25/09:38:32

Message-ID: <39A63C1E.927756BE@home.com>
From: Tom Fjellstrom <tfjellstrom AT home DOT com>
X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.15-4mdk i686)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: BAD strupr, BAD getw
References: <ue4cqsg0k83m0461605mnkssjo43odacen AT 4ax DOT com>
Lines: 27
Date: Fri, 25 Aug 2000 09:27:45 GMT
NNTP-Posting-Host: 24.70.88.2
X-Complaints-To: abuse AT home DOT net
X-Trace: news1.rdc1.ab.home.com 967195665 24.70.88.2 (Fri, 25 Aug 2000 02:27:45 PDT)
NNTP-Posting-Date: Fri, 25 Aug 2000 02:27:45 PDT
Organization: Excite AT Home - The Leader in Broadband
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Radical NetSurfer wrote:
> -------------- problem #2 getw() --------------
> 
> also,  getw is defined in LIBC.TXT as:
> 
> int getw(FILE *file);
> 
> this is INCORRECT!
> 
> get-WORD()  should of been defined as:
> 
> short getw(FILE*);
> 
> as a WORD is "typically/natively" DEFINED AS 16-BIT!
> 
> When did a WORD become PLATFORM SPECIFIC?

I belive It alwayse has been.
Generally On a 32bit chip a word is 32bits,
a 16bit chips word is 16bits, and a 64bit
cips word is 64bits.

a 'short' on the other hand has to be (?at least?) 16bits.

> DWORD == 32 bit == PC's for as long as anyone can remember!
> 
> I simply can not wait to hear the explanation for WORD being 16 bits.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019