i'm trying to write my own logging utility. is the...

# announcements

[william]

i'm trying to write my own logging utility. is there anyway to use reified functions / extension functions to automatically get the calling classes name?

something like

// usage
MyLogger.log("foo")

// impl
inline fun <reified T : Any> T.log(msg: String) {
  // ...
  val caller = T::class.simpleName
}

[Nir]

why are you assuming it's called from a class?

[nanodeath]

the way logging frameworks normally do that is using Thread.currentThread().stackTrace

[coroutinedispatcher]

Or you can just make it as an extension function from Any

[Tobias Berger]

what's wrong with your example code? Shouldn't that already work?

[flosch]

what's wrong with your example code? Shouldn't

that already work?

No, his code will always have MyLogger as caller

[flosch]

This is how I usually do it: https://github.com/floschu/control/blob/develop/control-core/src/main/kotlin/at/florianschuster/control/defaultTag.kt

[Tobias Berger]

ah, I see. If you define it as an extension function on a reified parameter, you should just call it directly on the instance you want as caller, not on the MyLogger object.

[Stephan Schroeder]

this article presents several options on how logging can be done in Kotlin. It’s where I got my approach from: https://www.baeldung.com/kotlin-logging

[Saul Wiggin]

Baeldung is a great resource.

[Nir]

This class orientation to logging is kinda odd in a language that advocates using free functions when appropriate

[Nir]

https://github.com/MicroUtils/kotlin-logging

[Nir]

Suggests having a file level logger

[Nir]

If you logger functions taking user lambdas are inlined and the lambda is reified, I believe you can ask the lambda which module/package it comes from

[Nir]

I have the code sitting somewhere

[Nir]

https://discuss.kotlinlang.org/t/how-get-package-name-inside-a-kotlin-file/4676

[william]

some of those paths wont work out outside of JVM