Another option I've found is using Kotlin Native.
https://kotlinlang.org/docs/reference/native-overview.html
It compiles Kotlin code directly to Apple frameworks for perfect
interoperability without the need of a JVM.
On Mon, Aug 26, 2019 at 6:41 PM Pier Bover wrote:
> Hi all
>
> In a couple o
If it’s any help: Microsoft Visual Studio now offers C++/winrt, a pure C++
environment that works great. Doesn’t seem to be well-known yet but it’s
efficient for Windows Store apps. So all our C++ code goes straight into the
Win version.
No need for C# or C++/CX, etc.
On the Mac I use C++ too ex
Writing that logic in C seems very intimidating to be honest, but thanks
for the suggestion.
A priori I think it would be less painful to maintain two codebases in
Swift and C#.
On Tue, Aug 27, 2019 at 1:44 PM Robert Tillyard
wrote:
> I had a UNIX project that was already in C that I ported to
> I had a similar dilemma in 2015 but went with C++, despite earlier bad
experiences with it. I've been happy with my choice; C++11 improved the
language quite a lot and C++17 even further
Hmm I might consider it. I did a couple of small C++ projects some years
ago before C++11 but I would be prac
> On Aug 26, 2019, at 4:41 PM, Pier Bover via Cocoa-dev
> wrote:
>
> I'd prefer avoiding C++ if possible.
I had a similar dilemma in 2015 but went with C++, despite earlier bad
experiences with it. I've been happy with my choice; C++11 improved the
language quite a lot and C++17 even furthe
