<div dir="ltr">Hmm.. v.out.ascii also uses * for all columns and g.mlist uses * for all mapsets and DEFAULT_WIND. I don't know why I thought there are "many" modules that use *.<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Jun 30, 2014 at 9:36 AM, Vaclav Petras <span dir="ltr"><<a href="mailto:wenzeslaus@gmail.com" target="_blank">wenzeslaus@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="">On Mon, Jun 30, 2014 at 9:19 AM, Glynn Clements <span dir="ltr"><<a href="mailto:glynn@gclements.plus.com" target="_blank">glynn@gclements.plus.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br>
Huidae Cho wrote:<br>
<br>
> Some modules also use * for a special case and I didn't have an<br>
> expansion problem with them either.<br>
<br>
</div>AFAIK, all the modules which currently use "*" do so because it's part<br>
of standard glob or regex syntax.<br>
<br></blockquote><div><br></div></div><div>I still think that I have seen somewhere usage of * in the meaning of NULL values. But by short search I found only:<br></div><div> </div><div>r.report <br></div><div> null String representing no data cell value<br>
default: *<br><br></div><div>This is output, so the command line issues are not present, the user confusion is.<br></div><div> <br><div>r.mask<br> maskcats Raster values to use for mask<br> format: 1 2 3 thru 7 *<br>
default: *<br> <br></div><div>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).<br>
<br></div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="">
For most utilities, using the shell's wildcard syntax makes the need<br>
for quoting inevitable (e.g. the find(1) manual page explicitly<br>
mentions this in relation to the -name, -iname etc options).<br>
<br>
GRASS "gets away with it" because of the option=value syntax and the<br>
fact that "=" is uncommon in filenames.<br>
<div><br>
> I think '--option value' is a valid point though. Are we going to<br>
> ever change option=value to --option value or planning to do so?<br>
<br>
</div>I doubt that we'd change it in the sense of abandoning support for the<br>
existing syntax, but modifying G_parser() to allow either form<br>
probably wouldn't require much work.<br>
</div><span class="HOEnZb"><font color="#888888"><span><font color="#888888"><br>
--<br>
Glynn Clements <<a href="mailto:glynn@gclements.plus.com" target="_blank">glynn@gclements.plus.com</a>><br>
_______________________________________________<br>
grass-dev mailing list<br>
<a href="mailto:grass-dev@lists.osgeo.org" target="_blank">grass-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/grass-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-dev</a><br>
</font></span></font></span></blockquote></div><br></div></div>
</blockquote></div><br></div>