Implicit variables, e.g. $_, are banned from my project. If you use a variable, you have to name it.
I agree with gramps on this one; implicit variables should be avoided ... but not to the extent of eschewing map, grep, sort etc.
I should note that i'm paid to develop commercial software, meaning i always have some junior developers come and go
Senior developers come and go too. What happens today at your company when you are away on leave? What is the company's succession plan if you decide to leave for greener pastures?
"The most perlish way" is nearly always a bad idea, whereas a C-like for loop is available in most languages.
It may depend on the company and its size, but I disagree with this general approach. In large companies I've worked for, it was common to have C++ specialists and Perl specialists. I would expect to see Perl code written idiomatically. Ditto for C++. And I would pull a face at code review if I spotted a C-style for loop in Perl code. :-)
Generally, I'm a fan of chromatic's emphasis on maintainability over "readability", described at Readability vs Maintainability References (update: note the classic "the determined Real Programmer can write FORTRAN programs in any language" and "thankfully there is not so much Fortranish Perl out there" quotes in hippo's reply ;-).
👁️🍾👍🦟
In reply to Re^4: 5.40 released
by eyepopslikeamosquito
in thread 5.40 released
by hippo
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |