Matt, there is a big difference between printing the stack trace and walking it
to find the info. printing it on every debug call would be insane.
Ralph
> On Jun 10, 2016, at 8:09 AM, Matt Sicker <boa...@gmail.com> wrote:
>
> Without Java 9, that's pretty much the only way to get the caller line
> number and other metadata besides the caller class.
>
> On 10 June 2016 at 09:44, Jochen Wiedmann <jochen.wiedm...@gmail.com> wrote:
>
>> On Fri, Jun 10, 2016 at 4:02 PM, sebb <seb...@gmail.com> wrote:
>>
>>> Depends on what the implementation does.
>>>
>>> For example:
>>>
>>> @Override
>>> void debug( String message ){
>>> new Throwable(message).printStackTrace();
>>> }
>>
>> Even a dumb application developer like me would at least like to see a
>> *bit* of performace. :-)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
>
> --
> Matt Sicker <boa...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
