Mirror of forum.nim-lang.org

1887 :: Swift's out, goodbye Objective-C backend?

• Zeno_X (orginal) [2015-12-22T16:17:08+01:00] view original

  Objective-C is still in the docs, but it's clearly deprecated for most use cases. Is anyone in the community following Swift's progress out of beta/the Apple island?

---

• Jehan (orginal) [2015-12-22T23:41:46+01:00] view original

  Objective C/C++ is going to be around for a long time. Not only can't Apple just kill backwards compatibility, too much of Apple's own code is written in Objective C to make a transition away from it a very long process. And many popular iOS frameworks (e.g., Xamarin's offerings) have interoperability code at the Objective C level.

  The cost of supporting Objective C as a separate backend for Nim is pretty minimal. I'd have to look at the compiler, but if it's much more than using .m instead of .c as the suffix for files and calling a different backend compiler, I'd be surprised.

---

• AnastasiaStefanuk (orginal) [2018-05-11T15:58:34+02:00] view original

  There are no ways to kill Objective C right now, as a lot of code was written on it. Ofc Swift is better, faster, and usable, but Apple needs a lot of time replace all. Here I found a little more about Objective C vs Swift

---

• yglukhov (orginal) [2018-05-11T16:26:04+02:00] view original

  I would happily get rid of objc support in the backend. Objc is pretty easy to bind to in library code and such code would have less problems than that generated by the objc backend. Example of a binding to NSDictionary that (a) doesn't depend on the headers, and (b) compiles and works in both C and CPP modes: https://github.com/yglukhov/darwin/blob/master/darwin/foundation/nsdictionary.nim

---

• JulsYa (orginal) [2019-08-14T14:48:18+02:00] view original

  Great! Thanks for this info)

---