# Static methods could convert better

**URL:** <https://discuss.kotlinlang.org/t/static-methods-could-convert-better/588>\
**Category:** Uncategorized\
**Created:** [April 27, 2014, 10:33pm UTC](https://discuss.kotlinlang.org/t/static-methods-could-convert-better/588 "2014-04-27T22:33:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikehearn](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/mikehearn/32/1424_2.png) [@mikehearn](https://discuss.kotlinlang.org/u/mikehearn)\
**Post date:** [April 27, 2014, 10:33pm UTC](https://discuss.kotlinlang.org/t/static-methods-could-convert-better/588/1 "2014-04-27T22:33:40Z")

</div>

I understand that class objects are Kotlin's approach to static methods and that they have some advantages. However, in practice what it means is when converting a java class with static methods, I have to go convert all the call sites (which are still in Java) from FooClass.method to SomePackage.method - makework I could do without.

It would be nice if there was a way to make class object methods that got mapped at the bytecode level to real Java static methods so API compatibility could be preserved.

---

<div class="post-metadata">

**Author:** ![abreslav](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/abreslav/32/8279_2.png) [@abreslav](https://discuss.kotlinlang.org/u/abreslav)\
**Post date:** [April 28, 2014, 9:32am UTC](https://discuss.kotlinlang.org/t/static-methods-could-convert-better/588/2 "2014-04-28T09:32:23Z")

</div>

Yes, we are considering a few approaches to this. One being annotating class object's methods so that they map to statics in Java, another — annotatins files/top level functions to emit classes other than FooPackage