Randal and Abigail sort of slammed your list as being too simplistic (which I'm sure it is for them and most of the people they work with), but I think it sounds fairly reasonable. If you're in a programming environment where you have Perl gurus in every cubicle who've been doing this stuff for years, sure, your list is too restrictive.

However, if you're in a programming environment where most of your Perl programmers are fairly new to the language (which I suspect is the case for many of us), I think your list is a good starting point to prevent at least some of the worst programming offenses.

Yes, it would be nice if we all worked with highly experienced people who eat, sleep, and breathe Perl every day, but we generally aren't that lucky. I think that in many shops, Perl programming is something that is done in addition to our "real" work. Having some basic "idiot lights" on the dashboard to help us avoid some of the most common problems can be helpful.

By the time you're surrounded by Perl gurus, you can come up with a different list (if you even need one at that point).

Wally Hartshorn