Hi Pavel, thanks for bumping this issue. I spent some spare minute to think about this idea and am inclined to walk along the path of this idea, but disagree on the finer details. Currently everyone can create an static extension class that implements this functionality as easy as that:
public static class ILogExtensions
public static void FatalExt(this ILog logger, object message)
and then call that extension as:
which semantically matches the statements:
but does not suffer from the flaws of lambda expressions (lambda expressions are hard to understand, odd stacktraces, programming with JIT while debugging, ..). We could of course add those extensions to log4net so everyone has them in future versions. Comments?