On Mon, Jun 30, 2014 at 9:19 AM, Glynn Clements <[email protected]>
wrote:
>
> Huidae Cho wrote:
>
> > Some modules also use * for a special case and I didn't have an
> > expansion problem with them either.
>
> AFAIK, all the modules which currently use "*" do so because it's part
> of standard glob or regex syntax.
>
>
I still think that I have seen somewhere usage of * in the meaning of NULL
values. But by short search I found only:
r.report
null String representing no data cell value
default: *
This is output, so the command line issues are not present, the user
confusion is.
r.mask
maskcats Raster values to use for mask
format: 1 2 3 thru 7 *
default: *
Manual does not say what * means. r.mask is using r.reclass, so if my
understanding is correct * should mean all remaining values but then the
format example does not make sense (or perhaps it does as a format
description, but not as an example).
For most utilities, using the shell's wildcard syntax makes the need
> for quoting inevitable (e.g. the find(1) manual page explicitly
> mentions this in relation to the -name, -iname etc options).
>
> GRASS "gets away with it" because of the option=value syntax and the
> fact that "=" is uncommon in filenames.
>
> > I think '--option value' is a valid point though. Are we going to
> > ever change option=value to --option value or planning to do so?
>
> I doubt that we'd change it in the sense of abandoning support for the
> existing syntax, but modifying G_parser() to allow either form
> probably wouldn't require much work.
>
> --
> Glynn Clements <[email protected]>
> _______________________________________________
> grass-dev mailing list
> [email protected]
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
