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

Huidae Cho grass4u at gmail.com
Sat Sep 6 05:33:59 EDT 2008


On Fri, Sep 05, 2008 at 12:18:10AM +0100, Glynn Clements wrote:
> 
> Markus Neteler wrote:
> 
> > >> > > 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).
> > >>
> > >> What is the current state? Since I have to deal with thousands of
> > >> maps in a mapset frequently, I am interested to get the g.mlist
> > >> and g.mremove scripts replaced with a C version.
> > >
> > > Well, first someone needs to find a regex library for Windows. If it's
> > > needed for g.mlist etc, it will effectively become a mandatory
> > > dependency, so if only source is available, we'll need to accept
> > > responsibility for providing a binary package.
> > 
> > Voila:
> > http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=73286
> > "Release Name: Current Release: mingw-regex-2.5.1
> > 
> > Notes:
> > This is a port of the GNU regex components from glibc,
> > ported for use in native Win32 applications by Tor Lillqvist.
> 
> I have added g.mlist and g.mremove to SVN trunk, along with
> G_set_ls_filter() and the configure checks for the regex functions.
> 

Do we really need to keep the old names (g.mlist/g.mremove) when we may
break backward compatibility in grass7?  The "m" used to stand for
"modified", but "extended" (g.xlist/g.xremove) would be more
appropriate.  Just my paranoia :-).

Huidae


More information about the grass-dev mailing list