logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaliy Kryvosheiev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-217) Delayed log
Date Fri, 28 Feb 2014 18:16:19 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916127#comment-13916127
] 

Vitaliy  Kryvosheiev commented on LOG4NET-217:
----------------------------------------------

Common.Logging already contains this feature

> Delayed log
> -----------
>
>                 Key: LOG4NET-217
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-217
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.10
>            Reporter: Fabio Maulo
>            Priority: Minor
>             Fix For: 3.5
>
>
> would be useful an override like this
> ILog.Debug(Func<string> messageDelegate);
> callable as
> log..Debug(()=> MyTimeExpensiveMethod);
> This is to prevent boiled code as
> if(log.IsDebugEnable)
> {
> log..Debug(MyTimeExpensiveMethod());
> }
> Log4Net can call the messageDelegate only when really needed.
> If you want stay in NET2.0 you can create a specific delegate
> public delegate string MessageDelegate;
> Btw, IMO, the new version should target directly .NET3.5.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message