In any case, if the message String does not give sufficient context to be able to understand where the message originated, then arguably it's not a very good message.
On 10 June 2016 at 16:34, Matt Sicker <[email protected]> wrote: > Oh, I didn't even notice the printStackTrace() part until now. Good point. > > On 10 June 2016 at 10:23, Ralph Goers <[email protected]> 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. >> >> Ralph >> >> > On Jun 10, 2016, at 8:09 AM, Matt Sicker <[email protected]> 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 <[email protected]> >> wrote: >> > >> >> On Fri, Jun 10, 2016 at 4:02 PM, sebb <[email protected]> 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: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> >> >> > >> > >> > -- >> > Matt Sicker <[email protected]> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Matt Sicker <[email protected]> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
