ObjC++
ObjC++
- Subject: ObjC++
- From: Thomas Lachand-Robert <email@hidden>
- Date: Tue, 4 Dec 2001 07:11:00 +0100
- Resent-date: Tue, 4 Dec 2001 16:03:34 +0100
- Resent-from: Thomas Lachand-Robert <email@hidden>
- Resent-message-id: <email@hidden>
- Resent-to: email@hidden
Eduardo,
I understand that you need to keep your C++ classes. If you fell good with
C++ and have to ensure portabilitiy, this is certainly a very reasonable.
But then I don't understand your problem, now. You can just use them and
mix with Obj-C classes freely (for Cocoa-specific things). That's exactly
the (huge) benefit of Obj-C++, and there is certainly a lot of people
doing that:
- model objects are usually platform independent, and written in C++ for
portability;
- view objects are ObjC because it's Cocoa (anyway there are usually
standard classes, or slightly modified);
- for controller objects, you can choose, but if you want a controller
inheriting from properties of NSWindowController for instance, or more
generally being the owner of a nib file, you need an Obj-C object. This
doesn't prevent you to have C++ members inside (from the STL or from your
code), and to use C++ features fully (except for the contructor problem I
explained in my previous message).
I somehow have the impression that you don't know about Obj-C++, do you? I
would suggest you take a look to
file://localhost/CubeX/Developer/Documentation/ReleaseNotes/Objective-
C++.html
Yours,
Thomas Lachand-Robert
********************** email@hidden
<< Et le chemin est long du projet ` la chose. >> Molihre, Tartuffe.