Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Wed, 30 May 2001 12:57:53 -0400 From: Christopher Faylor To: egor duda Subject: Re: isspace() & i18n Message-ID: <20010530125753.B19066@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: egor duda References: <13254193676 DOT 20010530145756 AT logos-m DOT ru> <20010530095254 DOT B17603 AT redhat DOT com> <9265832872 DOT 20010530181156 AT logos-m DOT ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from fujieda@jaist.ac.jp on Thu, May 31, 2001 at 01:29:28AM +0900 On Thu, May 31, 2001 at 01:29:28AM +0900, Kazuhiro Fujieda wrote: >>>> On Wed, 30 May 2001 18:11:56 +0400 >>>> egor duda said: > >> i think we should either conform to standard and explicitly convert >> types or define appropriate strings as unsigned char*, (typedef PATH_STR, >> perhaps), or define cygwin_is*() as macros that do the conversion, or, >> as glibc does, expand _ctype to allow indices in range [-128,256]. > >The last is preferable. > >The ISO C standard specifies is* facilities operate properly on >all values representable as type `char' and type `unsigned char'. >It depends on implementation whether char is signed or unsigned. >The is* facilities should operate on range [-128,256] on the >implementation where char is singied. I agree. I think that this is the preferable solution. Could someone take this discussion to the newlib mailing list? cgf