[
https://issues.apache.org/jira/browse/LOG4NET-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973264#comment-14973264
]
Stefan Bodewig commented on LOG4NET-482:
----------------------------------------
It might be in scope and had to be discussed on the dev list.
To be honest it looks as if the 1.3 branch was a dead-end and a new movement of
creating a fresh 2.0 without any compatibility burden and a lesser scope (in
particular a smaller number of supported frameworks) might be able to get more
traction.
> 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.3.0
> Reporter: NN
> Attachments: LOG4NET-482.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> 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)
