Jason Kohles wrote:
I do it like this...
use Catalyst (
( $ENV{ Catalyst::Utils::class2env( __PACKAGE__ ).'_STATS' } ? (
-Stats=1 ) : () ),
qw( Other Plugins Here ... ),
);
Interesting. When I do an %ENV dump comparison between starting the
devel server at the console and running it via t/*.t, about the only
obvious difference I could exploit is that *.t sets the HARNESS_ACTIVE &
HARNESS_VERSION keys, and console sets the CATALYST_ENGINE key.
Obviously the latter isn't going to work when I move to mod_perl or Fast
CGI for production, but presumably the HARNESS_* flags would be
reliable? It seems to work for now anyway, but I don't see anything in
%ENV matching class2env.
--
Richard Jones
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
