Re^2: Just before subroutine returns (depends)

Replies are listed 'Best First'.
Re^3: Just before subroutine returns (depends) by GrandFather (Saint) on Aug 29, 2017 at 21:03 UTC
Log statement for each of many returns or log statement for each of many execution branches comes to the same number of log statements if you are trying to determine execution sequence as is implied by OP's question. So there is no "logging" advantage to multiple returns here, and there are vast opportunities to make the flow of code clearer by using early exits. Multiply nested conditional code blocks and loops with a single exit: Yikes! (throws up hands and runs away). Premature optimization is the root of all job security	[reply]
Re^3: Just before subroutine returns (archive) by LanX (Saint) on Aug 29, 2017 at 16:17 UTC
We - or at least me - don't answer for the OP but for the archive. There are many possible cases where one needs to monitor subs, like e.g. needing to maintain foreign code and needing to figure out the intended mechanics. And PM is not Stack-Overflow, our strength is to have deep discussions not just singular case recipes. Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]
Re^3: Just before subroutine returns (depends) by iguanodon (Priest) on Aug 29, 2017 at 17:22 UTC
Maybe the OP didn't write the code, just inherited it.	[reply]