Message-ID: <006501bc604a$70167e60$4ff9c6c3@johans-dator> From: "Johan Henriksson" To: Subject: Re: Portability and size_t type related question Date: Wed, 14 May 1997 11:34:41 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Reply-To: djgpp AT delorie DOT com from Johan Henriksson, Sweden HTTP://come.to/jhewok | Primary mail: johan DOT he AT telia DOT com #UIN 12035895 Second: jhe75 AT hotmail DOT com Third: johan_he AT yahoo DOT com Leadprogrammer and FX-specialist at Real software http://come.to/real_software ************************************************************************* -----Original Message----- From: Guillermo Rodriguez Garcia Newsgroups: comp.os.msdos.djgpp To: djgpp AT delorie DOT com Date: Friday, May 14, 1999 10:41 AM Subject: Re: Portability and size_t type related question >El día Thu, 13 May 1999 17:15:36 +1000, Chris Mears > escribió: > >> >>> >>> > Like 'char' is always 1 byte. >>> >>> That's not true, either. There are compilers (mostly for embedded >>> systems) where `char' is 32-bit wide. >>> >> >>I thought the ANSI standard said that 'char' must be one byte wide. Am >>I wrong, or are those compilers non-standard? > >You are right. It is simply that a byte can be 32-bit wide for some >systems. Well, then all PC-compilers should use 8-bit=char so I think that's portable enough. I suppose we don't do any embedded systems here, or? > >Regards: >GUILLE >---- >Guillermo Rodriguez Garcia >XXguille AT XXiies DOT XXes (ya sabes :-) >