Re: How to use customized doc/gendocs_template

Bruno Haible writes: > Hi José, > >> In GNU poke we use the gendocs gnulib module. We also customize our >> doc/gendocs_template, which is committed in our VCS. >> >> This leads to the situation where each time we run `bootstrap', it >> copies the unmodified gendocs_template over to our tree, o

string-buffer: Remove INT_MAX limitation

This patch changes the string-buffer's *printf-based functions to use vsnzprintf instead of vsnprintf, thus - removing the INT_MAX limitation on the size of the result, - guaranteeing an errno value upon failure. (Recall that vsnprintf() does not guarantee an errno value when it fails.) 2

string-buffer: Link to vasnprintf implementation only when needed

Some uses of the 'string-buffer' module don't need the *printf implementation. In order to eliminate it from linking, when linking statically, this patch splits up the module into two compilation units. (The alternative would be a separate module 'string-buffer-printf', but that leads to an excess

Re: How to use customized doc/gendocs_template

Hi Bruno. I just pushed a fix in poke implementing the A) approach below. Thanks! > Hi José, > >> In GNU poke we use the gendocs gnulib module. We also customize our >> doc/gendocs_template, which is committed in our VCS. >> >> This leads to the situation where each time we run `bootstrap', i

Re: How to use customized doc/gendocs_template

Hi José, > In GNU poke we use the gendocs gnulib module. We also customize our > doc/gendocs_template, which is committed in our VCS. > > This leads to the situation where each time we run `bootstrap', it > copies the unmodified gendocs_template over to our tree, overwritting > the customized ve

How to use customized doc/gendocs_template

Hello people! In GNU poke we use the gendocs gnulib module. We also customize our doc/gendocs_template, which is committed in our VCS. This leads to the situation where each time we run `bootstrap', it copies the unmodified gendocs_template over to our tree, overwritting the customized version

new modules sf-istream, sfl-istream

The POSIX function fmemopen [1] is the way to create an input stream that reads from a string in memory. Unfortunately, it is not portable [2], and there is no way to make it portable (especially to native Windows) [3][4]. But some applications (e.g. GNU gettext) can make good use of such a constr