Re: Cross-Platform Windows plus Mac

On 2007-10-25 13:29:53 -0700, Ben Artin <macdev@[EMAIL PROTECTED]
> said:

> Objective-C++ is of questionable utility. At compile time, g++ 4 mode
has bugs
> that make some code that compiles when included from a .cpp file not
compile
> when included from a .mm file.

I'm very curious about what those specific bugs are, and whether 
they're addressed in the version of GCC 4.0.1 that's distributed with 
Xcode 3.

Several years back -- in the GCC 3.1 days -- I did some consulting work 
for a client with a huge (multi-million line) Objective-C++ 
application.  It worked quite well for their them and they were using 
modern C++ idioms at the time.

All they did was ensure that the layers were properly separated, i.e. 
that they didn't pass exceptions across the Objective-C/C++ boundary.  
By following that and a few other simple patterns, all of their logic 
(and there was a ton of it) was in C++ as was most of their 
"high-level" presentation code.  That in turn talked to Objective-C 
code which actually implemented the behavior for the high-level 
presentation code.

Today it would be even easier because you can do things like have 
constructors (zero-argument only, of course) and destructors invoked 
for non-pointer C++ objects that happen to be instance variables of 
Objective-C cl*****.  Of course, in the 32-bit runtime you still can't 
just throw exceptions across the C++/Objective-C boundary, but as 
Michael Ash points out, you can't do that with callback-based C APIs 
anyway.

  -- Chris