Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Fri, 7 Aug 2015 08:19:47 +0000 (UTC)
From: =?utf-8?Q?Mikael_St=C3=A5ldal_=28JIRA=29?= <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12707304.1397001509000.3070.1438935587758@Atlassian.JIRA>
In-Reply-To: <JIRA.12707304.1397001509000@Atlassian.JIRA>
References: <JIRA.12707304.1397001509000@Atlassian.JIRA>
 <JIRA.12707304.1397001509188@arcas>
Subject: [jira] [Commented] (LOG4J2-599) Support lambda functions (or
 similar) for log message parameters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/LOG4J2-599?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1466=
1487#comment-14661487 ]=20

Mikael St=C3=A5ldal commented on LOG4J2-599:
---------------------------------------

An argument for going with technology based name {{Java8Logger}} is that yo=
u might need to do it differently to achieve the same functionality with di=
fferent technologies.

{{Java8Logger}}, {{ScalaLogger}}, {{GroovyLogger}}, ...

On the other hand, it's probably better to differentiate them by different =
packages, and perhaps even different modules, and then you import the one y=
ou need.

I would prefer {{LazyLogger}} over {{LambdaLogger}} since you would most li=
kely use string interpolation and macros (rather than lambdas) to achieve i=
t in Scala.


> Support lambda functions (or similar) for log message parameters
> ----------------------------------------------------------------
>
>                 Key: LOG4J2-599
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-599
>             Project: Log4j 2
>          Issue Type: Brainstorming
>          Components: Core
>            Reporter: Matt Sicker
>            Priority: Minor
>              Labels: Java8
>
> It would be nice if we could support 0-param lambda functions (or the equ=
ivalent: interfaces with a single empty-parameter message call), or more si=
mply, allow Runnables (or something similar) to be passed which will be dyn=
amically executed if the log message is enabled.
> The use case here is that although string construction of the log message=
 is a performance issue that is already solved quite well, the problem of a=
dding in information to the log message that makes other calculations still=
 needs to be wrapped in an if check.
> I'm not sure if it'd be best to just use Runnable, or create a new interf=
ace, or try to emulate how Java 1.8 lambdas work via an interface with a si=
ngle method defined. The details here would still need to be fleshed out, b=
ut I think this sort of feature could be rather handy (especially in a Java=
 1.8+ environment, or in Groovy/Scala/etc.).


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

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org