The problem in that examples may not
embrace all if-trees
It's very quick to get samples clean
I hushed dozens of thousands warnings
but I'm not sure I cleared all code in 3
largest packages
Oleh
11 лютого 2017, 04:23:06, від "Allin Cottrell" <cottrell(a)wfu.edu>:
On Fri, 10 Feb 2017, Allin Cottrell wrote:
> On Fri, 10 Feb 2017, Allin Cottrell wrote:
>
>> On Fri, 10 Feb 2017, Sven Schreiber wrote:
>>
>>> Also, I think we should offer a little more support. A script that catches
>>> and perhaps even autocorrects the most common occurrences for example. As
>>> Oleh indicated, a "=" in the same line as an "if" for
example can only
>>> mean "==" I think (right?). (... outside of a foreign block, that
is....)
>>
>> The hansl parser knows what cases need fixing, but it doesn't have the
>> facility to change its input (or at least not so the change will be saved).
>> Hmm, may be worth investigating though.
>
> Having now looked into this, the answer's Sorry, no, far too complicated. The
> human brain and eyeball are the best tools for the job.
>
> There were huge warning counts for some packages, but that's because of
> iteration...
Case in point: all of the thousands of warnings generated for the
BMA package were generated by a single line of hansl, easily located
with the help of the warning message.
Allin
_______________________________________________
Gretl-devel mailing list
Gretl-devel(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-devel