Re: rename gl_FUNC_MBRTOWC

2008-12-17 Thread Ralf Wildenhues
Hello, * Bruno Haible wrote on Thu, Dec 18, 2008 at 03:28:16AM CET: > --- m4/mbrtowc.m4.orig2008-12-18 03:25:03.0 +0100 > +++ m4/mbrtowc.m4 2008-12-18 03:14:13.0 +0100 > @@ -9,6 +9,7 @@ > dnl This override of an autoconf macro can be removed when autoconf 2.60 or > dn

Re: rename gl_FUNC_MBRTOWC

2008-12-17 Thread Bruno Haible
Eric Blake wrote: > When overriding an autoconf macro, it is safer practice to wrap the > override with m4_ifndef or with m4_version_compare. That way, if a later > autoconf version changes the internal implementation to something that > works better, your override isn't trapping users with the ol

supporting autoconf < 2.60

2008-12-17 Thread Bruno Haible
This fixes an error when autoconf 2.59 and automake 1.9.6 are used. $ ./gnulib-tool --test quotearg ... executing autoconf configure:4339: error: possibly undefined macro: AC_COMPUTE_INT If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentatio

Re: rename gl_FUNC_MBRTOWC

2008-12-17 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 12/17/2008 4:57 PM: > > -dnl This file can be removed, and gl_FUNC_MBRTOWC replaced with > -dnl AC_FUNC_MBRTOWC, when autoconf 2.60 can be assumed everywhere. > +dnl This override of an autoconf macro can be removed when

Re: new module 'mbsinit'

2008-12-17 Thread Bruno Haible
Hey Paul! Paul Eggert wrote: > If I understand things correctly, this code is hijacking the underlying > system's mbstate_t type and using it for its own purposes? The idea > being that other gnulib code will be consistent with this? Yes, this is so. There is a comment that explains it: On these

Re: new module 'mbsinit'

2008-12-17 Thread Paul Eggert
Bruno Haible writes: > int > mbsinit (const mbstate_t *ps) > { > const char *pstate = (const char *)ps; > > return pstate[0] == 0; > } If I understand things correctly, this code is hijacking the underlying system's mbstate_t type and using it for its own purposes? The idea being that other

rename gl_FUNC_MBRTOWC

2008-12-17 Thread Bruno Haible
gl_FUNC_MBRTOWC has the same semantics as AC_FUNC_MBRTOWC. So it should be named the same. I'm applying this rename: 2008-12-17 Bruno Haible * m4/mbrtowc.m4 (AC_FUNC_MBRTOWC): Renamed from gl_FUNC_MBRTOWC. * m4/mbfile.m4 (gl_MBFILE): Use AC_FUNC_MBRTOWC instead of gl_F

new module 'btowc'

2008-12-17 Thread Bruno Haible
The next ISO C 99 multibyte/widechar function is btowc. 2008-12-17 Bruno Haible New module 'btowc'. * lib/wchar.in.h (btowc): New declaration. * lib/btowc.c: New file. * m4/btowc.m4: New file. * modules/btowc: New file. * m4/wchar.m4 (gl_WCHAR_H_

new module 'mbsinit'

2008-12-17 Thread Bruno Haible
I'm starting to add support for ISO C 99 multibyte / wide character functions, for systems such as HP-UX 11, IRIX 6.5, Solaris 2.6. The first module is 'mbsinit'. 2008-12-17 Bruno Haible New module 'mbsinit'. * lib/wchar.in.h (mbsinit): New declaration. * lib/mbsinit.c