Re: How should we override broken snprintf implementations?

On Thu, Feb 08, 2007 at 03:19:57PM -0800, Paul Eggert wrote: > "John McCabe-Dansted" <[EMAIL PROTECTED]> writes: > > > Hi, the pspp-dev@gnu.org team is wondering how to best handle the case > > where a broken native snprintf implementation (e.g. on mingw) > > prevents gnulib-tool from providing gn

Wrapping #include around #ifdef HAVE_CONFIG_H

Any reason all uses of #include aren't wrapped with #ifdef HAVE_CONFIG_H like so: #ifdef HAVE_CONFIG_H # include #endif Some .c files have the above and some don't. Seems to make sense for all to have the form above. -- albert chin ([EMAIL PROTECTED])

Re: Wrapping #include around #ifdef HAVE_CONFIG_H

Albert Chin <[EMAIL PROTECTED]> wrote: > Any reason all uses of #include aren't wrapped with #ifdef > HAVE_CONFIG_H like so: > #ifdef HAVE_CONFIG_H > # include > #endif > > Some .c files have the above and some don't. Seems to make sense for > all to have the form above. The vast majority

Re: time_r.h -> time_.h

Bruno Haible <[EMAIL PROTECTED]> writes: > But I would find it good to wait a month or so, to stabilize the idioms > used in and string_h.m4. Another option is to pick one of those files, time.h say, and try another idiom with it. That way we can gain experience with whether a simpler idiom wil