commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [crypto] Logging dependency
Date Sat, 11 Jun 2016 08:59:57 GMT
On 11 June 2016 at 06:34, Ralph Goers <ralph.goers@dslextreme.com> wrote:
>
>> On Jun 10, 2016, at 2:56 PM, Torsten Curdt <tcurdt@vafer.org> wrote:
>>
>>> 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.
>>>
>>
>> Why would anyone want to do that?
>>
>> https://docs.oracle.com/javase/7/docs/api/java/lang/StackTraceElement.html
>>
>>
>> And how do you think the logging frameworks get that kind of information? :)
>
> I think you missed Sebb’s suggestion of having the debug method call printStackTrace().

I was just pointing out that using a shared debug method does not lose
the original caller information, as it can be derived from the call
stack.
I was not suggesting that anyone would actually use that code.

> Ralph
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

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


Mime
View raw message