in reply to RFC: pragma 'use dev;'

A simple idea: a single pragma to switch between development and production code behaviour.

You seem to be saying that switching off logging, strict and warnings in production code would be a good idea?

I find that a curious suggestion - since I'd want them there more than anywhere else.

Replies are listed 'Best First'.
Re^2: RFC: pragma 'use dev;'
by rvosa (Curate) on Aug 26, 2006 at 17:00 UTC
    Thank you all for your comments. I think I should clarify that I probably didn't mean that none of strict, warnings, logging etc. should be used in production. But I do think that many people have different configurations for dev versus production.

    I can only really speak for myself, so in my case, in production, I use strict, but no warnings or diagnostics (e.g. in libraries). I set logging (Log::Log4perl) to 'warn' rather than 'info' or 'debug'. For cgi programming, I like to have fatals go to the browser when debugging, but not when the site is in production. The idea was that you could switch easily between such different configurations.

    I like the suggestion of using environment variables to specify what these configurations are, thanks.
[reply]

In Section Meditations