Re: Objective-C or Objective-C++
Re: Objective-C or Objective-C++
- Subject: Re: Objective-C or Objective-C++
- From: Markus Hitter <email@hidden>
- Date: Fri, 3 Feb 2006 16:47:51 +0100
Am 03.02.2006 um 15:55 schrieb John Stiles:
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.
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 :)
Having two halves is fine and the intended use of Obj-C++.
What have you got against mixing the two?
I've once seen a tutorial mixing both languages a lot more than
glueing two parts together and at the end of this tutorial the mess
was already complete, e.g. using NSException inside an C++ exception,
calling -dealloc in destructors, avoiding autorelease, and so on. I
can't recommend such use of the two-in-one compiler Obj-C++,
especially not for beginners.
objc++ is a compiler which happens to understand two distinct
languages at once, IMHO. This is useful because both languages share
the same core, C.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
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