From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: BAD strupr, BAD getw Date: 27 Aug 2000 17:30:33 GMT Organization: Aachen University of Technology (RWTH) Lines: 20 Distribution: world Message-ID: <8obj7p$e4o$1@nets3.rz.RWTH-Aachen.DE> References: <2mncqsos70c6u5losbrrlrq9qq2esrm9t0 AT 4ax DOT com> <200008262246 DOT SAA18823 AT envy DOT delorie DOT com> <487iqsk8i7aivpinll7098bi1rbgsee517 AT 4ax DOT com> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 967397433 14488 137.226.32.75 (27 Aug 2000 17:30:33 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 27 Aug 2000 17:30:33 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Damian Yerrick wrote: > On Sat, 26 Aug 2000 18:46:52 -0400, DJ Delorie wrote: >>I've seen machines where char, short, and long are all 32 bits. > If char is 32 bits, then text files and HTML files must be _huge_ on > those machines ;-) Not necessarily. You can make use of the freedom given to the implementor of an ANSI/ISO standard C compiler to store each char of a file opened in text mode as 8 bits, expanding to 32 bits transparently inside the functions. Just because a char is 32 bits inside a C program doesn't mean it has to be 32 bits on disk, too. OTOH, the typical everything-is-32bits-wide hardware of these days is found in embedded systems, which hardly, if ever have such 'highlevel' features as a file system :-) -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.