The part "objc++ is completely unmaintained" is a little worrisome.
Can I assume that it is stable/usable? I need it only to allow my app
to use existing C++ code in various libraries. Apart from
instantiating the existing C++ objects and invoking their methods from
within my Objective-C code, I really won't be doing any new C++ code.
Mike
On May 7, 2009, at 2:23 AM, David Ayers wrote:
Am Donnerstag, den 07.05.2009, 06:56 +0000 schrieb David Ayers:
Am Mittwoch, den 06.05.2009, 13:07 +0100 schrieb David Chisnall:
On 4 May 2009, at 21:28, Mike Simmons wrote:
Is your compiler built with Objective-C++ support? This is not
the
default for building GCC, and many distributions are reluctant to
enable it because it is not really maintained by anyone at the
moment. Can you compile a simple ObjC++ file?
Is gcc Objective-C++ support distinct from ordinary Objective-C
support? I can compile and run a simple Objective-C program but not
an Objective-C++ program.
Yes, in GCC objc and objc++ are entirely distinct front-ends. This,
unfortunately, means that improvements in one do not always get
shared
with the other, and that while objc is almost-unmaintained, objc++
is
completely unmaintained.
Well, if you look at how the front-ends are implemented, objc++
actually
links in many of the object files of the objc front end, so most pure
objc features/fixes do get shared.
Actually, that's not quite correct... the objc++ front end actually
re-compiles the objc front end file.
Yet objc++ is indeed in need of a maintainer.
_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep