Date: Sat, 30 Aug 2003 12:16:00 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp AT delorie DOT com Message-Id: <8011-Sat30Aug2003121600+0300-eliz@elta.co.il> X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: <3F4FE557.3090104@acm.org> (message from Cesar Rabak on Fri, 29 Aug 2003 20:44:23 -0300) Subject: Re: wide character functions References: <2427-Thu28Aug2003000602+0300-eliz AT elta DOT co DOT il> <8296-Thu28Aug2003162425+0300-eliz AT elta DOT co DOT il> <3F4E90EF DOT 33122DA4 AT phekda DOT freeserve DOT co DOT uk> <2110-Fri29Aug2003133636+0300-eliz AT elta DOT co DOT il> <3F4FBDDF DOT 85DA1F2B AT phekda DOT freeserve DOT co DOT uk> <3F4FE557 DOT 3090104 AT acm DOT org> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: Cesar Rabak > Newsgroups: comp.os.msdos.djgpp > Date: Fri, 29 Aug 2003 20:44:23 -0300 > > > > I don't understand how is* can support multibyte characters, when > > they only take an int argument. > > > Since an int in DJGPP is 32 bits, I can see how, though I'm not sure it > does. As four bytes seems to me 'multibyte' (four in fact ;-). No, the standard clearly says that the int argument to the is* macros must be either representable as an unsigned char, or be the value of EOF. So multibyte characters are out.