> On Nov 11, 2019, at 6:15 AM, Turtle Creek Software via Cocoa-dev > <cocoa-dev@lists.apple.com> wrote: > > Then suggest that Cocoa would work better if Obj-C were a > superset of C++ rather than plain C. Objective-C++ all the way down, not > just in source files.
Obj-C++ is a superset of C++, so I’m not sure what you’re wishing for. There’s even pretty good interoperability between C++ and Obj-C objects: for example you can embed the former as an ivar, or make vectors of Obj-C classes. > Objective-C and Cocoa will be deprecated soon, replaced by > Swift and SwiftUI. That way there is just one shiny new closed system for > all Apple hardware. So much simpler. You can’t really call it “closed” when the entire Swift toolchain and runtime libraries are open source, portable, and being actively used on other platforms. That’s more open than Obj-C, because Apple never open-sourced Foundation. And it’s much more open than the platform you’re decamping to. MSVC and .NET are both fully closed, as far as I’m aware. And I doubt C++-to-C# integration is that much smoother. —Jens _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
