in reply to Re: "next" in Parallel::ForkManager, and subroutines
in thread "next" in Parallel::ForkManager, and subroutines
I think the point here is: next does exactly what it always does. What’s peculiar at first glance is the use of “short circuit” expression evaluation as a substitute for clarity.
You see the same sort of thing in statements like: do_something() or die(“horribly”); What sounds like a not-so veiled threat, is actually just short-circuit again. If do_something() returns true, the die() part will not be executed.
Call me a luddite or simply a non-golfer, but I never write it that way. I don’t mind using two statements where one statement will do, if by doing so I will eliminate the need for threads like these. To me, perfect clarity always trumps brevity, and there is no place in the world of engineering for religion (or golf).