Re: Objective-C or Objective-C++
Re: Objective-C or Objective-C++
- Subject: Re: Objective-C or Objective-C++
- From: John Stiles <email@hidden>
- Date: Fri, 03 Feb 2006 06:55:07 -0800
Markus Hitter wrote:
Am 02.02.2006 um 16:55 schrieb Rick Langschultz:
I was wondering if I should use objective-c or Objective-C++.
Using Obj-C++ without a need for it is asking for trouble, IMHO.
Am 02.02.2006 um 17:58 schrieb Paul J. Lucas:
The Objective-C part of Objective-C++ is exactly the same. The
latter allows C++ syntax, but adds nothing to the "Objective-ness".
Well, some people started to use C++ inside Obj-C intentionally.
Something like "Use Obj-C classes within C++ and use C++ classes
within Obj-C, whatever fits your need at hand best". The resulting mix
is a mess, IMHO. Not to mention the slow compile times and suboptimal
runtime performance.
Um, this sounds like a personal bias to me.
A lot of people use C++ for their cross-platform app logic, and Obj-C
for their GUI. Obviously, when the two halves meet, Obj-C++ comes into
play :) It's been a joy for me... I can write app logic using my
preferred language, and GUI code using Apple's preferred language, and
the app runs great. I haven't seen any compile-time or run-time penalty;
the generated C++ code looks the same as always, and the generated Obj-C
code looks the same too. If you are fluent in the languages, and you use
an ounce of common sense, it's as clean and well-factored as any language.
What have you got against mixing the two?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden