If you wish to solve the problems you perceive to exist, you should join an Objective-C/Objective-C++ email list or hire developers experienced in those nuances. -- Gary
> On Nov 11, 2019, at 10:47 AM, Turtle Creek Software via Cocoa-dev > <cocoa-dev@lists.apple.com> wrote: > > >> >>> Obj-C++ *is* a superset of C++, so I’m not sure what you’re wishing for. > > In source files Obj-C++ works great. No complaints there. But headers and > method declarations are Obj-C, which is C plus its own additions. > > 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 multiple > inheritance, so we had to duplicate code in several places. No > initializing members in headers, so mystery bugs if you initialize in the > wrong type of init. 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. > > Make Objective-C a complete superset of C++ rather than C and it gains all > the fantastic work that has gone into C++ over the past 20 years. Take > advantage of folks from many places working on the language, not just half > or 1/4 of the engineers at Apple. > > Casey McDermott > TurtleSoft.com > _______________________________________________ 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
