That's certainly one approach. You could write something like:

use My::App::Logging;
....
sub foo : Logger {
  ...
};
[download]

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.