[GRASS-dev] G_message () family of functions

[Ivan Shmakov]

>>>>> Glynn Clements <glynn at gclements.plus.com> writes:

 >>>> + vsprintf (buffer, template, ap);

 >>> It would be nice to use vsnprintf(), but we would need to check
 >>> that it's available (it's not in C89).

 >> ... And to use Gnulib-provided one if it isn't?

 > I wouldn't bother adding an additional dependency.

	But how on Earth could Gnulib be an additional dependency?

--cut: http://www.gnu.org/software/gnulib/--
    Gnulib is a central location for common GNU code, intended to be
    shared among GNU packages. GCC has libiberty, but this is hard to
    disentangle from the GCC build tree. libit proved too hard to keep
    up to date, and at this point is moribund.

    Gnulib takes a different approach. Its components are intended to be
    shared at the source level, rather than being a library that gets
    built, installed, and linked against. Thus, there is no distribution
    tarball; the idea is to copy files from Gnulib into your own source
    tree.
--cut: http://www.gnu.org/software/gnulib/--

 > Given the large size of the GRASS codebase and the relatively small
 > number of developers, pragmatism wins over perfectionism.

	Are they conflicting, or rather complementing each other in this
	particular case?