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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
