Re: [bug-gnulib] Question concerning c-ctype, c-strcase, c-strcasestr and c-strstr modules

2006-11-14 Thread Yoann Vandoorselaere
On Tue, 2006-11-14 at 14:58 +0100, Bruno Haible wrote: Yoann Vandoorselaere wrote: I don't think Chinese users will find it nice if you exclude them from correct functioning of your program because of performance or library size. I don't think you are qualified to decide in place

Re: [bug-gnulib] Question concerning c-ctype, c-strcase, c-strcasestr and c-strstr modules

2006-11-14 Thread Yoann Vandoorselaere
On Tue, 2006-11-14 at 13:38 +0100, Bruno Haible wrote: Yoann Vandoorselaere wrote: However, if we have a platform missing strcasestr, then using c_strcasestr as the substitute implementation is probably okay, because that platform would probably be broken in other areas, such as locale

Re: [bug-gnulib] Question concerning c-ctype, c-strcase, c-strcasestr and c-strstr modules

2006-11-14 Thread Bruno Haible
Yoann Vandoorselaere wrote: I don't think Chinese users will find it nice if you exclude them from correct functioning of your program because of performance or library size. I don't think you are qualified to decide in place of the application developer whether the application should

Re: [bug-gnulib] Question concerning c-ctype, c-strcase, c-strcasestr and c-strstr modules

2006-09-15 Thread Bruno Haible
Yoann Vandoorselaere wrote: The c-ctype, c-strcase, c-strcasestr and c-strstr modules seem only to implement their replacement functions using a c_ prefix. However, there is no autoconf test implemented by these modules that redefine the original function (in case it is missing) to point to