I have a project targeting JVM and Native where I ...
# multiplatformp
pajatopmr
11/27/2018, 11:49 AMI have a project targeting JVM and Native where I want to “expect” a File and then typealias the actual but I am beginning to think this might not be possible. How might I accomplish my goal of using the name “File” in both common and JVM code?
t
thevery
11/27/2018, 12:17 PMactual typealias File = java.io.Filep
pajatopmr
11/27/2018, 12:27 PMTried that, no joy. I saw that @kpgalligan tried something similar with no joy as well and worked around the issue so I followed his lead, fwiw.
i
ilya.gorbunov
11/27/2018, 1:11 PMWhat problems have you struggled with? Something with mapping expect properties to Java getters?
o
olonho
11/27/2018, 7:15 PMWhat do you want to typealias File on Native to?
k
kpgalligan
11/27/2018, 7:16 PMHey, missed this thread. Sorry.
kpgalligan
11/27/2018, 7:17 PMThe issue with typealias depends on what you're defining in the expect class
kpgalligan
11/27/2018, 7:17 PMIf you're defining a method that is protected in Java, it won't work, even though it seems like it should. There's a bug filed for this that's been outstanding for a while. It'll take a bit to dig up...
p
pajatopmr
11/27/2018, 7:18 PMI want the native code for Win/Lin/Mac to use a posix file type, CValuePointer or some such if memory serves as the aliased type, .e.g. actual alias File = CValuePointer
pajatopmr
11/27/2018, 7:19 PMThe expect declaration is “expect typealias File”
k
kpgalligan
11/27/2018, 7:19 PMThe expect is typealias? Didn't know that was a thing.
p
pajatopmr
11/27/2018, 7:20 PMIt might not be. 🙂
pajatopmr
11/27/2018, 7:21 PMBut it seemed like a good idea at the time.
k
kpgalligan
11/27/2018, 7:22 PMFor the record, the visibility issue is here: https://youtrack.jetbrains.net/issue/KT-19848
kpgalligan
11/27/2018, 7:22 PMThat's not the issue you're having.
kpgalligan
11/27/2018, 7:23 PMYou'd need to define what the 'File' object should do in expect, then implement in actual. That implementation might point to posix, but you need to implement it. You can have a single 'native' implementation, but all target platforms would need to have access to the posix file api
kpgalligan
11/27/2018, 7:25 PMI'm not proud of this, but I did a copypasta for quick and dirty file ops in knarch: https://github.com/touchlab/knarch.db/tree/master/kotlin/knarch-ios/src/main/kotlin/co/touchlab/knarch/io
kpgalligan
11/27/2018, 7:26 PMA more adult local file library would be super cool. Happy to provide some support if you're building that 🙂
p
pajatopmr
11/27/2018, 7:29 PMYes, I hope I am. Thanks for the link.
k
kpgalligan
11/27/2018, 7:30 PMAh. That was so long ago. I was delegating to posix.Forgot
kpgalligan
11/27/2018, 7:31 PMJust a heads up. The file/folder listing calls bomb (I think, at least sometimes)
p
pajatopmr
11/27/2018, 9:11 PMFor the JetBrains @olonho folks, is “expect typealias Foo” a thing or wishful thinking on my part?
pajatopmr
11/27/2018, 9:18 PMI think I now understand: one would use “expect class File” and realize this for JVM by “actual typealias File = java.io.File”
👌 1
o
olonho
11/28/2018, 5:18 AMYes, expect typealias shall work, but POSIX file APIs provide different level of abstraction compared to
java.io.File