Log::Log4perl has these levels–
OFF FATAL ERROR WARN INFO DEBUG TRACE ALL
In Catalyst/Log::Log4perl::Catalyst I just pick what makes sense at the time. Fatal and error both sort of define themselves. Warn is something important for the dev to see early and often until fixed. Info… seems a step too much but I have used it when waffling about using debug. Debug for normal, easy to understand flow information that is possible,
or prone, to regressions/problems. Trace, the whole enchilada, too much really but some trouble shooting requires it. All… I don’t even think is supported in Catalyst logging… never saw it before tonight.
-
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.
|
