Am 30.10.2015 um 02:32 schrieb Allin Cottrell:
On Thu, 29 Oct 2015, Allin Cottrell wrote:
> On Thu, 29 Oct 2015, Sven Schreiber wrote:
>
>>
>> <hansl>
>> bundle b
>> b.cutoff = 0.05
>> ols lhs const rhs1 rhs2
>> omit --auto=b.cutoff
>> </hansl>
>>
>> Instead 'omit' will use the default value of 0.10 in this case.
>
> This should not fail silently, agreed. Now in git it fails noisily:
>
> ? omit --auto=b.cutoff
> b.cutoff: invalid option argument
Well, OK, it might as well succeed since it's not that difficult to
arrange. That's now in git.
Hm, I'm not sure that's the best course of action. We had the issue
before that "you pay a price for the simplicity of commands". For example,
var b.lagorder series1 series2
isn't possible, either.
IMHO either bundle elements (of the right type, of course) should be
possible everywhere, or they should be banned everywhere. Of course I'd
like the "possible everywhere" option, but I can understand that it's
difficult and error-prone. So I would rather have a clearcut rule;
explicit errors are not a problem in my view. Any partial solution isn't
helpful for really mastering hansl.
thanks,
sven