[GRASS-dev] Re: [GRASS-user] g.xlist/g.xremove addons (C version of g.mlist/g.mremove)

[Ivan Shmakov]

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

 >> I've just uploaded g.xlist and g.xremove (C implementations of
 >> g.mlist and g.mremove, no dependency on g.list/g.remove) to
 >> grass-addons/general.  To compile these addons, you need POSIX
 >> regex(3) functions.  They are super fast (native speed of
 >> g.list/g.remove)!  Please test these modules.

[...]

 >> If these changes to libgis (ls.c, join.c, gisdefs.h, POSIX regex)
 >> are acceptable, g.m?(list|remove) might be substituted with these
 >> modules (?).

 > The existing scripts cannot be removed unless the C versions can be
 > made to work on all platforms (I daresay there's a regex library for
 > Windows, but we still need configure tests, etc).

	BTW, Autoconf allows for the parts of the package to be
	configured by independent `configure' scripts
	(AC_CONFIG_SUBDIRS.)  Could the splitting of the top-level
	`configure' script be considered for GRASS?

	Doing the things this way has the following benefits:

	* the move to Autoconf 2.50 could then be made gradually, and
	  not at once;

	* when the part of code depends on a set of specific libraries,
	  there won't be any need to collect the specific compiler and
	  linker flags into specific variables -- they could be
	  collected into CPPFLAGS, CFLAGS and LDFLAGS (thus simplifying
	  the script), while they'll affect only the part of the package
	  the configure script belongs to.

[...]