note coolmichael I sat through a code review a few months ago. It was my first time, and quite the experience. The person's CGI script started just like yours does above. Then, about thirty or so lines in, there was <code> $filename =~ m/(.*)/gi; $filename = $1; open FILE, "$filename"; </code> I was shocked, as this was code written by a "professional." I can count about six errors in those three lines of code.<p> <ol> <li> Poor taint checking (none really.) <li> Not checking if the match succeeds. I guess it doesn't matter if it's just matching [deat to dot star|dot star]. <li> Not checking if the open succeeds. <li> Should use the three form of open <li> The match is stupid. dot-star doesn't care about case insensitivity (/i). <li> The match is really stupid. /g is (i think) for trying to match multiple times in a loop. This doesn't do that. </ol> <p>You are quite right, warnings, strict, CGI, and taint are a good start. But you do need to still read the code before you use it. I don't think there is anything to help avoid a good code review. <p> <b>update</b>: The programmer still works there. I don't, by my own choice.</p> --<br> <a href="www.negativespace.net">negativespace.net</a> - all things inbetween. 233900 233936