Hi Eric.
On Wed, 7 Oct 2009, Eric Blake wrote:
> Yes. But in my opinion, it is even slicker to use either the
> xvasprintf{-posix} module, which mallocs for you and calls xalloc_die
> automatically on malloc failure:
>
> char *buf = xasprintf (format, args);
>
> or the vasnprintf{-posix} modul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[moved to bug-gnulib; I accidentally posted the patch series to bug-coreutils]
According to Eric Blake on 10/7/2009 11:00 AM:
> Eric Blake byu.net> writes:
>
>> The patch copies from areadlink.c, as well as link_follow earlier in
>> linkat.c, to cre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I noticed these minor issues today, so I'm pushing this. I'm now heavily
entrenched in trying to write utimensat, and it's turning into quite a
project.
- --
Don't work too hard, make some time for fun as well!
Eric Blake e...@byu.net
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ian Beckwith on 10/7/2009 5:27 PM:
>>> With ./gnulib-tool --create-megatestdir --with-tests,
>>> fseek fails to compile when combined in ALL/ with any of:
>>> fwritable fwritable-tests or fwriting.
>> Previously reported. Thanks for furth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Joel E. Denny on 10/7/2009 5:25 PM:
> Hi.
>
> I have a couple of questions about gnulib's support for the printf family.
>
> 1. Is the snprintf-posix module helpful in order to use the following
> portably?
>
> length = snprintf (NUL
On Mon, Oct 05, 2009 at 02:37:07PM +, Eric Blake wrote:
> Wrong.
> Wrong.
Oops.
> > With ./gnulib-tool --create-megatestdir --with-tests,
> > fseek fails to compile when combined in ALL/ with any of:
> > fwritable fwritable-tests or fwriting.
>
> Previously reported. Thanks for further cla
Hi.
I have a couple of questions about gnulib's support for the printf family.
1. Is the snprintf-posix module helpful in order to use the following
portably?
length = snprintf (NULL, 0, format, args);
str = malloc (length + 1);
snprintf (str, length + 1, format, args);
The snprintf man
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I noticed that mkdirat didn't have any tests. While I didn't find any
systems where mkdirat is implemented and mkdir("dir/") fails (which would
imply that we need rpl_mkdir), I did find that cygwin 1.5 and mingw have
bugs where mkdir("dir/./") mistake
Hi Eric,
Eric Blake writes:
> The circle was:
> ./getopt.h did include_next
> did include , but found ./unistd.h
> ./unistd.h did include_next
>completed
> ./unistd.h did include , and found ./getopt.h
>./getopt.h declared things
> ./unistd.h completed
> redeclared things
>
>
