Thank you especially to extremely for pointing out the specific case that is a red flag, the $varN thing.
Also, what's a red flag anyway? A lot of you seemed to interpret it as "if you do this, you're a bad programmer" which is certainly not how I saw it at all.
To me a red flag is more like "that way works, sure, but did you know there's a much easier way?". Or in fact, it's maybe "that works, but you don't have to write code that way in Perl -- who told you you did?".
How about this example, to stimulate further discussion.
When I first started, the only way I knew how to iterate through an array was
but I would never do that any more. It looks horrible to me, plus, extra variables, more syntax to go wrong, scary for beginners and so on.for ($x=0;$<@array;$x++){ # .. do something with $array[$x] }
Is that a red flag? It shows either that the person's a refugee from another, less accomodating language, or it shows that they've learned from sources that don't understand how easy iterating through an array is in Perl.
Maybe it's just red flags for beginners that I'm interested in, er, flagging..?
--
Every bit of code is either naturally related to the problem at hand, or else it's an accidental side effect of the fact that you happened to solve the problem using a digital computer.
M-J D
In reply to Re: Should We Have A "Red Flags" Area?
by Cody Pendant
in thread Should We Have A "Red Flags" Area?
by Cody Pendant
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |