News for hackers. Stuff that matters.
Re:Swift and C++ interoperability workgroup announcement by grayprog on Tuesday February 01, 2022 @11:27AM (#30164827)
I see, so you're just writing the bridge code yourself. OK, I do the same in Objective-C++, so at least it gives me an object-based interface, as well. But saving this step and having a direct Swift <-> C++ would be helpful.
Re:Swift and C++ interoperability workgroup announcement by jb1991 on Tuesday February 01, 2022 @11:34AM (#30164984)
Yeah for me it's just about keeping Obj-C out of the project. It's enough to have two languages, I don't want to unnecessarily add a third.
Re:Swift and C++ interoperability workgroup announcement by quux on Wednesday February 02, 2022 @09:33AM (#30178064)
Don't you already have 3 languages to think about? Swift, C and C++?
Re:Swift and C++ interoperability workgroup announcement by jb1991 on Wednesday February 02, 2022 @11:04AM (#30179411)
The C API is usually syntactically valid C++, so I don’t think of it that way. It’s just an API. Implementation is still in just two languages.