[GRASS-dev] requring explicit input=-

Michael Barton michael.barton at asu.edu
Sat Sep 24 12:35:10 EDT 2011


On Sep 25, 2011, at 8:17 AM, <grass-dev-request at lists.osgeo.org> wrote:

> Date: Sat, 24 Sep 2011 13:46:37 +0200
> From: Martin Landa <landa.martin at gmail.com>
> Subject: Re: [GRASS-dev] requring explicit input=-
> To: Hamish <hamish_b at yahoo.com>
> Cc: grass-dev at lists.osgeo.org
> Message-ID:
>        <CA+Ei1Oc1hE7+gc8HYVCfEek_16_tTcs7eKJHup2W0efPi=5T-g at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> 2011/9/24 Hamish <hamish_b at yahoo.com>:
>> re. r48434 ?(and a number of other places)
>> 
>> it's a PITA to have to type input=- all the time from the command
>> line in places where it can be readily inferred.
> 
> well, I don't think that it's a PITA, it's just a little bit more
> typing, in this case `i=-` ;-) Personally I would incline to force
> user to define that stdin should be read. It leads to the more
> readable module interface and probably less confusing for CLI
> newcomers. What's your opinion, GRASS power users?


On Sep 25, 2011, at 8:17 AM, <grass-dev-request at lists.osgeo.org> wrote:

> Date: Sat, 24 Sep 2011 16:34:00 +0200
> From: Martin Landa <landa.martin at gmail.com>
> Subject: Re: [GRASS-dev] Re: requring explicit input=-
> To: Hamish <hamish_b at yahoo.com>
> Cc: grass-dev at lists.osgeo.org
> Message-ID:
>        <CA+Ei1Od6c-PtN-qy1KuK5ZVAoutGKM9Fj3=Qjr=Q5-krjapTRA at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> 2011/9/24 Hamish <hamish_b at yahoo.com>:
>> can anyone think of a case where "-" would ever be used as an
>> arbit'rary string, not meaning stdin?
>> I guess it is a similar probability to someone wanting to use a
>> literal "-" as a file or map name. g.message is all I can think
>> of, but that's not used in the gui menu.
> 
> I don't know, anyway this rude check can be always replaced by full
> check (gtask.parse_command/interface). wxGUI is quite over-complicated
> (too much commands running on the background), let's try a simple
> check first (without checking type of the options).

I agree with Martin in both cases.

Michael


More information about the grass-dev mailing list