You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2015/10/25 13:11:27 UTC

[jira] [Commented] (LOG4NET-482) ILog Format methods with exception

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

Stefan Bodewig commented on LOG4NET-482:
----------------------------------------

This would be a backwards incompatible change (breaking existing implementations of ILog) and thus is out of scope for 1.2.x.

> ILog Format methods with exception
> ----------------------------------
>
>                 Key: LOG4NET-482
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-482
>             Project: Log4net
>          Issue Type: Improvement
>    Affects Versions: 1.2.13, 1.2.14, 1.3.0
>            Reporter: NN
>         Attachments: LOG4NET-482.patch
>
>
> I suggest adding **Format methods which receive Exception as a first parameter.
> It will create an ambiguity in call of log.TraceFormat(null, ...) since null is convertible both to IFormatProvider and Exception but this case is pretty rare.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)