wow things are moving fast! nice!

@jmfayard has left the channel

@kropp Well done.

Great job, thanks Victor! Would be cool to see complete bindings.

@kropp great post.

One question about the static click handler of the button class. I am neither a master of gtk, nor am i a master of Kotlin native. To be honest, even my C is rusty 😉 Is there a problem in never explicitly unregistering the static handler in the button class?

@uli you're right, this sample lacks proper resource management. I omitted this for brevity, but full featured bindings should of course unsubscribe signals and free memory allocated for pointers

next step: jni with kotlin on both sides of the bridge

rewrite the linux kernel in android 😉

not sure if either of those are best things to do 🙂. Kotlin looks like great application level language, not system software language. Anyway, let’s see how things will go.

ahh keep quiet 😉 😍

i'd really love there to be an object/class level native API, so that we wouldnt have to keep falling back to C bindings whenever we dont have a vm

unfortunately C++ is very difficult to work with

oh yeah =(

did it for years, never wanna go back

kotlin btw gives me the same feeling for Java 😄

i wouldnt mind writing the low level stuff in rust or what have you and application code in kotlin, if there were a way to do it without void * erasure

few minutes of kotlin and you start to forget semicolons in Java

well, maybe we could think of some sort of bridge, the hardest part is object level interoperability between different languages/runtime, usually people want to pass more than just integers and strings between worlds

@olonho agreed, its not an easy problem. gobject introspection is the closest thing i've seen to a interoperable object model thats at the native level. unfortunately, its something of a mess cross-platform (and rather slow, last i looked at it)

D has some limited non-template C++ bindings that worked pretty well, but at some point you simply cant bind C++ beyond simple code that was specifically written to be interoperable

I love D for native stuff

not sure it’ll stay after kotlin-native keeps up 😄

some level of compatibility with C++ could be achieved, however I’m not sure if it’s a good thing 😉

well, the guys from Project Panama might bring the main way to do it for free 🙂

they have C++ interoperability already in the Panama Prototype

however haven’t yet had a look how they handle the mangling

yeah im not sure C++ bindings would do anything for me. more library availability in the short term sure, but long term i wish there were a sane object model at the native level that made interop possible. its one of the best things the jvm and CLI have going for them

I was unable to find details, if Project Panama allows C++ object-level interoperability, do you know if it’s the case?