{ prototype / parsing issues }I fail to see your point here. There's nothing implicite going on here. sin takes an argument, and hence what follows is parsed as an expression (so the slash is the start of a regex). time doesn't take an argument, hence what follows is parsed as an operator (so the slash is a division).
Confusing for people who can't deal with context sensitive tokenizers, but that has nothing to do with implicite things.
Not putting a 'return' before the last statement of a subroutine isn't ambiguous either. The last expression executed in a subroutine will be the value returned from that subroutine. Always. Without exception.Why is it OK to use implicite arguments for shift?Because it isn't ambiguous.
It seems to me that you think Perl gives one too much rope to hang yourself. That's ok. I think Perl does that for the majority of the coders. But I also think that if you find Perl too scary, or that if you want to limit yourself to a small subset of Perl because there are many features you find confusing or unclear, you should stop programming in Perl, because your mindset just doesn't fit Perls. Nothing wrong with that, there are many other languages that will fit you better.
In reply to Re^12: "advanced" Perl functions and maintainability
by Anonymous Monk
in thread "advanced" Perl functions and maintainability
by geektron
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |