[MacPorts] #71517: kermit @9.0.302: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]

[MacPorts]

#71517: kermit @9.0.302: error: type specifier missing, defaults to 'int'; ISO C99
and later do not support implicit int [-Wimplicit-int]
-----------------------+---------------------
  Reporter:  SaintBol  |      Owner:  (none)
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.10.5
Resolution:            |   Keywords:  sequoia
      Port:  kermit    |
-----------------------+---------------------

Comment (by tmcintos):

 Replying to [comment:9 ryandesign]:
 > Replying to [comment:6 shpokas]:
 > > Pardon my ignorance but why can't this issue be solved like this
 comment:ticket:70755:11 instead of going back to developers of kermit?
 >
 > That ticket worked around the problem in that port by downgrading the
 errors back to warnings again.

 ... which is exactly what is needed right now to get people up and going.

 > But compiler makers deliberately upgraded these warnings to errors in
 recent years because they are bad programming practices, already
 disallowed by the 1999 version of the C standard over a quarter century
 ago. Future compilers might not allow this error to be downgraded. The
 best solution is to fix the code. The people to do that are the developers
 of the software so the problem needs to be reported to them so that they
 can do that and release a fixed stable version.

 Sorry, but this is irrelevant. None of this matters when you have users
 down and you have a perfectly workable solution in-hand.

 The focus should be on the users here. What we need right now is to fix
 this regression. It doesn't have to be the best solution. You can work on
 that after the immediate problem is fixed.

 There is a ton of legacy C code in the world that is not going anywhere
 anytime soon, so I'd be very surprised to see K&R support yanked from
 compilers in the near future. At least it seems like a pretty dumb idea to
 me. It makes sense to discourage people from writing new K&R style C code
 by making this an error by default, but arguing that 30+ year old stable
 code must be rewritten for no other reason than to update the style is
 dumb.

-- 
Ticket URL: <https://trac.macports.org/ticket/71517#comment:13>
MacPorts <https://www.macports.org/>
Ports system for macOS