Guy English
Swift Protocol Proposal http://kickingbear.com/blog/archives/521 …
-
@Kickingbear@gte We have limitations that make writing and working with those abstract types ugly, but we're not done yet.
Joe Groff
@Kickingbear @gte ObjC and the ObjC runtime also aren't going away. Using @objc for things still we suck at natively is good and encouraged.
-
-
@jckarter "aren't going away" My intuition says they'll naturally wither like Carbon did. And we won't mind. -
@wilshipley Carbon may be gone, but Clang still supports Pascal strings, m68k packing, four-char codes, ... -
@jckarter LA LA LA I CAN'T HEAR YOU.
-
-
-
@jckarter@Kickingbear@gte@objc@brentsimmons we have too much legacy code including a lot of ObjC++ to switch -
@mike3k You don't have to rewrite from scratch. Swift can mix-and-match with C and ObjC code (though C++ is still a problem). - View other replies
-
@jckarter our VOIP code is C++ and the parts that interface to it are ObjC++
-
-
@jckarter But it's nice to hear there aren't plans to artificially axe ObjC. -
@jckarter@Kickingbear@gte Glad Apple is informally making this clear. Lot's of fear in the community around that previously. -
@jckarter would be scary otherwise@olebegemann@Kickingbear@gte@objc
Wil Shipley
Mike uǝɥoƆ
Colin Cornaby
Omar Abdelhafith
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.