Having taken a look at Log:Log4perl, it seems to me that using it and Carp::Assert in combination is entirely the wrong thing to do. If you want to log warnings use the WARN category of Log4perl messages.

The whole point of Carp::Assert (from my reading) is that it is designed for testing fail conditions from which there is no recovery and that when it is switched off, it has minimum impact on the script that uses it.

It's design criteria, and the idea of permenently enabling it to log Warning conditions seem to be fundementally in conflict?

--- demerphq
my friends call me, usually because I'm late....

See Log::Log4perl and this article for info.

sub assert ($;$) {
    unless($_[0]) {
        require Carp;
        Carp::confess( _fail_msg($_[1]) );
    }
    return undef;
}
[download]

If you don't use Carp::confess elsewhere, you could override it to call Log::Log4perl.