[GRASS-dev] v.mapcalc missing UI

GRASS GIS GRASS GIS developer
1

Hi,

does anyone know how v.mapcalc should work? It seems to me that the
module lacks an UI, no options, no G_parser(). It leads to the fact
that

v.mapcalc --help

just freezes. I blacklisted this module in r66406 from addons
generation. It means that this module lacks its description in
modules.xml [1] which is used by `g.extension`. It will remain like
that otherwise someone fix this module or GRASS parser.

Martin

[1] https://grass.osgeo.org/addons/grass7/modules.xml

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

2

On Sun, Oct 4, 2015 at 11:53 AM, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

does anyone know how v.mapcalc should work? It seems to me that the
module lacks an UI, no options, no G_parser(). It leads to the fact
that

v.mapcalc --help

just freezes. I blacklisted this module in r66406 from addons
generation. It means that this module lacks its description in
modules.xml [1] which is used by `g.extension`. It will remain like
that otherwise someone fix this module or GRASS parser.

I suppose that a similar job as once done for r.mapcalc has to be done:
https://trac.osgeo.org/grass/changeset/32578/grass/trunk/raster/r.mapcalc

FYI - here some historic notes about the v.mapcalc development:

https://lists.osgeo.org/pipermail/grass-user/2002-May/006639.html (and
subsequent emails)
https://lists.osgeo.org/pipermail/grass-dev/2002-July/thread.html#5931
https://lists.osgeo.org/pipermail/grass-dev/2002-August/006075.html

Markus

3

Martin Landa wrote:

does anyone know how v.mapcalc should work? It seems to me that the
module lacks an UI, no options, no G_parser(). It leads to the fact
that

v.mapcalc --help

just freezes.

v.mapcalc reads the expression from stdin (see yylex.c); argv is
ignored.

Not only does it not call G_parser(), it doesn't call G_gisinit()
either. The only GRASS functions which it calls are:

G_calloc
G_malloc
G_realloc
G_fatal_error
G_free
G_gettext
G_message
G_warning

I suspect that it's probably a long way from being functional at
present.

--
Glynn Clements <glynn@gclements.plus.com>