Don't have the docs handy, but OOTOMH, 'UseStrict' simply implies that use strict; would be at the top of every perl script that mod_perl handles, whether explicitly there or not. It doesn't protect any variables in any way. Of course, I will assume you already have use strict; at the top of every perl file you've written, don't you? :)

Don't try to drop in the entire project at one shot; start with non-DB-destructive files like search routines or lookups, and make sure these work and apply any bug fixes that you need to across all project files. While it's a lot easier to build a site that will use mod_perl in an environment that already users mod_perl from scratch, existing scripts that use good perl programming practices should be able to drop in without any major gotchas, but there will always be a few.

---

Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain