On Mon, May 21, 2018 at 08:07:03PM -0500, Mike Blackwell wrote:
> This particular patch addresses the warning caused by falling off the end
> of a subroutine rather than explicitly returning.
Do we really want to make that a requirement? Making sure that there is
a return clause if a subroutine returns a result makes sense to me, but
making it mandatory if the subroutine does not return anything and
callers don't expect it do is not really a gain in my opinion. And this
maps with any C code.
Just today, I coded a perl subroutine which does not return any
results... This is most likely going to be forgotten.
--
Michael