Re: Thoughts on Objective-C++
Re: Thoughts on Objective-C++
- Subject: Re: Thoughts on Objective-C++
- From: Jens Alfke via Cocoa-dev <email@hidden>
- Date: Mon, 11 Nov 2019 14:33:09 -0800
> On Nov 11, 2019, at 10:46 AM, Turtle Creek Software <email@hidden>
> wrote:
>
> That means no use of const. All pointers instead of & references. Both of
> those are good at turning run-time errors into compile-time. […] No
> public/private to manage access. Etc. It was like going back to the early
> 90s. Doing without features we learned to use the hard way.
Well yes, Obj-C is not a very good C++, just as C++ isn't a very good Obj-C.
And Haskell isn't a very good Ruby, and vice versa.
I like C++ and use it daily, but I could write a litany of complaints about it
compared to Obj-C and Swift — C++ has meager reflection/introspection, its
collection and string APIs are horrendous, it has weak and awkward support for
memory management, templates are a super-kludgy [SFINAE, OMG] way to implement
generics, it promotes writing unreadable code, etc.
I'm not just joking here. Obj-C's dynamic nature is at the heart of a lot of
Cocoa's powerful features like Interface Builder and KVO. Super-static
languages like C++ don't work well for GUI development, IMHO, because they make
it hard to compose high-level objects together.
—Jens
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden