According to Bruno Haible on 10/30/2007 7:23 PM:
>
> Installed:
>
> 2007-10-30 Bruno Haible <[EMAIL PROTECTED]>
>
> * modules/xprintf-posix: New file.
Plus this followup, so that tests will pass on cygwin (xprintf pulls in
xalloc-die, which requires gettext).
From: Eric Blake <[EMAIL P
Jim Meyering wrote:
> > introduce a module 'xprintf-posix' that causes xprintf to have POSIX
> > semantics for the formatted output. It will depend on xprintf and
> > vprintf-posix. I'll do it later today if you don't beat me to it.
>
> That makes sense.
> It will be less invasive, too.
> Thanks.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 10/20/2007 10:31 AM:
>> is there a better way to just automatically update po/Makevars (possibly
>> by teaching po/Makevars how to include a second file)?
>
> Not so far. But what I could do in the next gettext release is
> 2007-10-20 Bruno Haible <[EMAIL PROTECTED]>
>
> * modules/error (Notice): Mention how to augment the XGETTEXT_OPTIONS.
> * modules/vasprintf (Notice): Likewise.
> * modules/xprintf (Notice): Likewise.
> * modules/xvasprintf (Notice): Likewise.
I now applied this. Augme
Jim Meyering wrote on 2007-10-20:
> Here's what I want :-)
>
> Simply add an attribute to each affected module indicating that a
> function takes a printf-style format string, and then let tools do
> the rest, possibly even including deriving the arg offset based on
> attribute dir
Jim Meyering wrote on 2007-10-20:
> ... just saying "out of memory" provides
> no clue as to which output file may have just been corrupted
> as a result of this failure. Nor does it mention that the error
> arose during an attempt at formatted output.
>
> I'll bet we have enough of the pieces to
Jim Meyering meyering.net> writes:
> Bruno Haible clisp.org> wrote:
>
> Both sound good.
> I'll fix it tomorrow if no one beats me to it.
I did it today, along with my patch to add xvprintf.
--
Eric Blake
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Eric Blake wrote:
>> > Any objection to making this module also provide xvprintf and xvfprintf?
>> > M4
>> > has a use of vfprintf, which would be nice to have the wrapper for.
>>
>> As in the following? (Also, it fixes a C89 compiler issue).
>
> Fine w
Eric Blake wrote:
> > Any objection to making this module also provide xvprintf and xvfprintf?
> > M4
> > has a use of vfprintf, which would be nice to have the wrapper for.
>
> As in the following? (Also, it fixes a C89 compiler issue).
Fine with me. Just nitpicking:
- I would call the lo
Eric Blake <[EMAIL PROTECTED]> wrote:
>> Jim Meyering meyering.net> writes:
>> > I've just added a new module:
>> >
>> > http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=78da34d40e6a2
>>
>> Any objection to making this module also provide xvprintf and xvfprintf? M4
>> has a use of vf
Eric Blake byu.net> writes:
>
> Jim Meyering meyering.net> writes:
>
> >
> > I've just added a new module:
> >
> > http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=78da34d40e6a2
>
> Any objection to making this module also provide xvprintf and xvfprintf? M4
> has a use of vfp
Jim Meyering meyering.net> writes:
>
> I've just added a new module:
>
> http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=78da34d40e6a2
Any objection to making this module also provide xvprintf and xvfprintf? M4
has a use of vfprintf, which would be nice to have the wrapper for.
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Eric Blake wrote:
>> gnulib-tool output is already verbose
>
> It was mentioned that verbosity can be overcome by looking at the differences
> between the previous run and the current run. I use the attached script daily.
>
>> is there a better way to just
Eric Blake wrote:
> gnulib-tool output is already verbose
It was mentioned that verbosity can be overcome by looking at the differences
between the previous run and the current run. I use the attached script daily.
> is there a better way to just automatically update po/Makevars (possibly
> by te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 10/20/2007 8:22 AM:
> So that this doesn't get forgotten in the future, I propose this patch. It
> has the effect that gnulib-tool reports:
gnulib-tool output is already verbose; is there a better way to just
automatically
Bruno Haible <[EMAIL PROTECTED]> wrote:
>> I've just added a new module:
>>
>> http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=78da34d40e6a2
>
> gnulib-tool gives these warnings when the module is used:
> warning: module xprintf depends on a module with an incompatible license: exit
>
Jim Meyering wrote:
> I've just added a new module:
>
> http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=78da34d40e6a2
Note that the XGETTEXT_OPTIONS will need to be updated to take into account
these new functions that take a format string as argument.
So that this doesn't get forg
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Thanks; this module is necessary.
>
> Two suggestions:
>
> - Add a call to va_end() that matches the va_start() call. POSIX says:
> "Each invocation of the va_start() and va_copy() macros shall be matched
>by a corresponding invocation of the va_end()
Hi Jim,
> I've just added a new module:
>
> http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=78da34d40e6a2
gnulib-tool gives these warnings when the module is used:
warning: module xprintf depends on a module with an incompatible license: exit
warning: module xprintf depends on a mo
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Jim Meyering wrote:
>> On this subject, I'm nearly convinced that we need printf and fprintf
>> wrappers that call fseterr when necessary. That would be cleaner and
>> more maintainable than doing s/printf/xprintf/ everywhere.
>
> I disagree. When you cal
Jim Meyering wrote:
> On this subject, I'm nearly convinced that we need printf and fprintf
> wrappers that call fseterr when necessary. That would be cleaner and
> more maintainable than doing s/printf/xprintf/ everywhere.
I disagree. When you call fseterr, you lose information about the origin
Hi Jim,
> I've just added a new module:
>
> http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=78da34d40e6a2
Thanks; this module is necessary.
Two suggestions:
- Add a call to va_end() that matches the va_start() call. POSIX says:
"Each invocation of the va_start() and va_copy() m
Jim Meyering <[EMAIL PROTECTED]> wrote:
> I've just added a new module:
>
> http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=78da34d40e6a2
>
> It was prompted by this thread:
>
> http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/11611/focus=11620
On this subject, I'm nearly co
I've just added a new module:
http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=78da34d40e6a2
It was prompted by this thread:
http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/11611/focus=11620
24 matches
Mail list logo
