[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gawk] lint Option Future

From: M
Subject: Re: [bug-gawk] lint Option Future
Date: Wed, 22 May 2019 14:45:45 +0300

Thank you for a fast feedback!

No, the only thing under consideration is to be able to disable the "foo is a 
gawk extension" warnings somehow, keeping the others present. Nothing more.
Perhaps, it would be useful for a society too.


Yours respectfully,
Mark Krauze

22.05.2019, 12:47, "address@hidden" <address@hidden>:
> Hi.
> M <address@hidden> wrote:
>>  Are there any plans to develop the --lint option?
> Not really. As a general statement, I am trying to spend less of
> my life on gawk and more of it on other things...
>>  I've read in the manual that there is a mode "invalid"
>>  (i.e. --lint=invalid) which is not fully implemented yet.
> There's only one place at the moment where an "invalid" check is
> performed. "Not fully implemented" thus means that there are undoubtedly
> many more places where such checks could be performed, but haven't been.
>>  For instance, one knows that he/she uses some features which are specific
>>  to gawk.
>>  When using the --lint option without a value, one can see a sheet of 
>> warnings:
>>  .........
>>  "THIS_FEATURE is a gawk extension"
>>  "AND_THIS_FEATURE is a gawk extension"
>>  .........
>>  --lint is quite useful to determine simple faults.
>>  As far as I understand, there is no way to get rid of these warnings at
>>  the moment.
> If all you want is to be able to disable the "foo is a gawk extension"
> warnings, I can probably do that without too much effort.
> If, on the other hand, you want something more elaborate, then either
> you'll have to find someone else to do the work, or consider financing
> my doing it.
> Thanks,
> Arnold

reply via email to

[Prev in Thread] Current Thread [Next in Thread]