Re: Long array -> multiple columns?

A couple of general tips.

When modifying a global for local use (e.g. $_), localize it first.
I don't see $i declared. Is strict on?
Almost always, C-style loops are much harder to read and maintain then their Perl equivalents.
Consider using for my $i (a..b) instead of for (my $i=a; $i<=b; $i++).
If you want to hide a warn, why not just hide *that* warning. e.g. no warnings 'uninitialized';

Comment on Re: Long array -> multiple columns? Select or Download Code

Replies are listed 'Best First'.
Re^2: Long array -> multiple columns? by azredwing (Sexton) on Jan 30, 2008 at 06:46 UTC
$i was previously declared, I should have mentioned that. This is a snippet of the entire code. Like I said, I only just learned Perl. I learned C last semester and the stuff I do at my work is a lot of string-manipulation stuff so that's why I switched. I wrote the initial thing when I was still making the transition from C to Perl -- I'd basically write C code with Perl. I'm getting much better at coding Perl-style-Perl but it's been a month. I also did not know I could hide specific warnings. Thanks.	[reply]
Re^3: Long array -> multiple columns? by ikegami (Patriarch) on Jan 30, 2008 at 06:52 UTC
The reason I mentioned `$i` is that you reuse the variable (not just the name). I typically view that as bad, especially when it's trivial to declare it for the loop itself. `\|\| vv for my $i (1..5) { ... }` [download]	[reply] [d/l] [select]