Re: [bug-gawk] lint Option Future

[M]

   Actually, the situaltion you've described reminds me my trouble. My
   colleages and I have cleaned up the scripts with --lint=fatal. Most
   probably, we should leave it in the tests if it had kept silence
   (somehow) in case of gawk extensions. "foo is a gawk extension" are the
   only warnings we see in the logs.

   A

   22.05.2019, 15:16, "Wolfgang Laun" <address@hidden>:

   I used to work in an environment where compatibility was an issue. But
   there was common consent that, once you leave POSIX (or some otherA
   catechism) behind and use the extensions some language implementation
   provides, you have declared explicitly not to care any more about being
   compatible. Consequently, being pestered with warnings about using an
   extension is IMHO completely superfluous.
   A
   The SW safety pundits are advocating checks using a tool from the lint
   pedigree whenever they are available, but they also require you to
   address each message resulting from such runs. Messages of the kind
   addressed by this thread would be a nuisance.
   A
   My 2A-c-...
   Wolfgang
   A

     A

   On Wed, 22 May 2019 at 11:51, <address@hidden> wrote:

     Hi.
     M <address@hidden> wrote:
     > Are there any plans to develop the --lint option?
     Not really.A  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
     A

References

   1. mailto:address@hidden
   2. mailto:address@hidden