Comment, comment, comment. If you interdisperse enough plain english (or whatever spoken language) amongst your code, it will look less like line noise and more like reasonable coding. In particular for lines that may seem to be 'line noise' due to just how perl handles them, in this case the regex lines, and the sort call. It makes it easy for the non-perl programmers to understand the logic here.
Avoid using the 'shortcut' identifiers like $_ and $1, at least, assign other more descriptive variable names to these values, and if you have to specifically say what those are, comment them as well. It might add overhead, but if you need to design for maintainence and usability of the code, it's probably worth the tradeoff.
For functions like open, exists, etc, where the parans around the arguments aren't necessary, it might help those more used to C and other languages to use parens to group arguements appropriately, such that they look less like 'loose words' and more like function calls.
In reply to Re: Trying to avoid line noise (brain cramp)
by Masem
in thread Trying to avoid line noise (brain cramp)
by Ovid
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |