[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnulib] gettext vs. gnulib

From: Paul Eggert
Subject: Re: [Bug-gnulib] gettext vs. gnulib
Date: 23 Dec 2003 12:19:43 -0800
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3

address@hidden (Karl Berry) writes:

> - I guess we should not resync vasprintf.c.

I agree.  There's a ChangeLog entry for that:

   2003-10-30  Paul Eggert  <address@hidden>
               Bruno Haible  <address@hidden>

           * vasprintf.c: Include <limits.h>, <stdlib.h>.
           (vasprintf): Fail if the resulting length doesn't fit in an 'int'.

Evidently this change didn't get into gettext; perhaps a backsync
problem (i.e., the change should have been propagated back to gettext
but wasn't for some reason)?

> - I'm not sure what to make of the vasprintf.h diff.

That's logged as follows.

   2003-01-30  Bruno Haible  <address@hidden>

           * vasprintf.h: New file, from GNU gettext with modifications.

Evidently the modifications are there on purpose, so I'd leave them in.
(I don't know why they weren't merged back into gettext.)

> - The only differences in [un]setenv.c is ANSI stuff; if Bruno is
>   eventually going to go ANSI for those, I'm inclined to prefer syncing
>   to ANSIfication, but certainly won't insist.

These changes were logged as follows, so I'd leave them in for now
too.  (Perhaps another backsync problem?)

   2003-09-10  Bruno Haible  <address@hidden>

           * setenv.c: Include <stdlib.h> and <string.h> unconditionally.
           * unsetenv.c: Likewise.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]