That's certainly one approach. You could write something like:
use My::App::Logging;
....
sub foo : Logger {
...
};
and the logging functionality is encapsulated into My::App::Logging, and the attribute handler wraps the method appropriately.
However, an AOPer would comment that you lose some of the benefits that an aspect based approach would give you:
- You still have to add the handler to every method you want logged. If you change the policy on what should or should not be logged you still have to do a lot of manual work.
- You lose the benefit of having the logging "aspect" documented/implemented in one place.
-
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.
|
