Here's a new module that adds a function quotearg_file:
like quotearg_buffer but it writes the output to a FILE
instead. This prevents additional memory allocation if you
are quoting large data. And it provides a simpler API.
Regards,
Oskar Liljeblad (os...@osk.mine.nu)
diff -u1 ChangeLog.v0
On Wednesday, March 05, 2008 at 11:26, Simon Josefsson wrote:
Hi!
Hi! I wanted to use the 'byteswap' gnulib module in libntlm (licensed
under LGPLv2), but it didn't work:
gnulib-tool: *** incompatible license on module byteswap: LGPL
The reason is that the 'byteswap' module says the
On Monday, October 16, 2006 at 20:32, Eric Blake wrote:
Hi Eric!
OK to apply this patch, to conform with the majority of gnulib that
assumes config.h?
Of course!
Oskar
instead of one
all the time, or create another set of functions accepting a
'size_t n_null_bytes' argument.
Regards,
Oskar Liljeblad ([EMAIL PROTECTED])
:39:14 -
@@ -1,6 +1,7 @@
-/* Arithmetic.
- Copyright (C) 2001-2002 Free Software Foundation, Inc.
+/* Greatest common divisor.
+ Copyright (C) 2001, 2002, 2006 Free Software Foundation, Inc.
Written by Bruno Haible [EMAIL PROTECTED], 2001.
+ Made generic by Oskar Liljeblad [EMAIL
I think the human module depends on xstrtoumax, not xstrtol.
Regards,
Oskar
2005-10-12 Oskar Liljeblad [EMAIL PROTECTED]
* modules/human: Depend on xstrtoumax, not xstrtol.
diff -u modules/human.v0 modules/human
--- modules/human.v02005-10-12 21:02:11.0 +0200
+++ modules
On Wednesday, October 05, 2005 at 18:12, Bruno Haible wrote:
I just noticed that the 'stdint' module was GPL. Would it be possible
to re-license it?
Yes, done (assuming Oskar's agreement).
Of course, I don't think I coded anything in it anyway (I only came
up with the idea).
Regards,
Normally you're supposed to add LIBOBJS, LIBICONV, LIBINTL, ALLOCA etc to
*_LIBADD/LDADD. But are these still necessary when using Gnulib (and the
appropriate modules such as iconv, gettext, alloca)?
Oskar
___
bug-gnulib mailing list
they like with it (for example, including it in glibc
under a changed license if necessary).
Good. I think I signed assign.future (at least it is almost identical
to the template GNU assign.future documents found on the net).
Regards,
Oskar Liljeblad ([EMAIL PROTECTED
to be signed as well first?
Regards,
Oskar Liljeblad ([EMAIL PROTECTED])
___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib
On Wednesday, August 24, 2005 at 15:52, Bruno Haible wrote:
I'm not in favour of a wrapper around malloc(), that would add overhead to
a function called as frequently as malloc(), just to set 'errno'.
ISO C 99 is not a substandard, and Windows malloc() is not poor just
because it does not
I don't know if this is necessary or necessarily correct, but
it seems getdelim doesn't always set errno on failure (when it
returns -1).
From what I can tell, the test below (needed cur_len) is to
test for overflow.
Oskar Liljeblad ([EMAIL PROTECTED])
Index: getdelim.c
On Tuesday, August 23, 2005 at 17:59, Jim Meyering wrote:
Oskar Liljeblad [EMAIL PROTECTED] wrote:
I don't know if this is necessary or necessarily correct, but
it seems getdelim doesn't always set errno on failure (when it
returns -1).
From what I can tell, the test below (needed
/vl_lib_readline.html
It also mentions libedit and libeditline (apparently those are other
GNU readline-like implementations).
Regards,
Oskar Liljeblad ([EMAIL PROTECTED])
___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug
for ({ and found other modules using the same syntax,
but when looking closer I realize that they provided non-GCC versions
for all macros as well. Doing TEMP_FAILURE_RETRY without macros won't
work...
So let's drop this idea...
Regards,
Oskar Liljeblad ([EMAIL PROTECTED
),
for precisely that reason.
I get that warning without both -W and -Wall, I think.
(gcc 3.3.6)
Regards,
Oskar Liljeblad ([EMAIL PROTECTED])
___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib
(GCC) 3.3.6 (Debian 1:3.3.6-6)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$
Regards,
Oskar Liljeblad ([EMAIL PROTECTED
What's the proper way to fix these warnings?
quotearg.c: In function `quotearg_n_options':
quotearg.c:586: warning: comparison is always false due to limited range of
data type
argp-help.c: In function `make_hol':
argp-help.c:430: warning: comparison is always true due to limited range of
data
file be
called? comparison_fn.h? compfn.h? cmpfn.h?
Regards,
Oskar Liljeblad ([EMAIL PROTECTED])
___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib
to put config.charset under build-aux/, the Makefile
rule would become more complicated because it would have to refer to
the build-aux/ dir (which can be ../build-aux/ or ../../build-aux/ or worse).
I see. Its name, config.charset, was misleading me...
Regards,
Oskar Liljeblad ([EMAIL PROTECTED
,
int (*) (const void *, const void *));
Sure, but assume you're passing strcmp for the comparison function,
wouldn't you want to cast it to avoid the warning?
Regards,
Oskar Liljeblad ([EMAIL PROTECTED])
___
bug-gnulib mailing list
bug
21 matches
Mail list logo
