I figure that more aggressive warnings are usually better than less aggressive. If you get warnings that you decide are not warranted, then you can "crank down the warning level" for that segment of code, but usually (in my opinion) that's the wrong thing to do unless you are extremely clear about why you are going that.
As far as parm validation goes, there is a whole bunch that didn't get talked about for this code example....use of prototypes in Perl functions, etc. In this case the issue was defined or not which is different than say param #3 should be between 4 and 12.
In any event, I think that it is wrong to return silently when the sub fails.
Update: In any event, I think that it is wrong to silently return a valid return value when the sub fails.
In reply to Re^3: Modifying Arrays passed by reference to subroutine
by Marshall
in thread Modifying Arrays passed by reference to subroutine
by sadarax
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |