Re: Cross-Platform Windows plus Mac

In comp.sys.mac.programmer.help Ben Artin <macdev@[EMAIL PROTECTED]
> wrote:
> In article <1193193656.328993@[EMAIL PROTECTED]
>,
> Michael Ash <mike@[EMAIL PROTECTED]
> wrote:
> 
>> You use Objective-C++ for the code that has to call into C++, and you
wrap 
>> the C++ calls with exception handlers, just like you would do if the
GUI 
>> code were C++. Seems no harder than it would be in something like Qt.
Am I 
>> wrong?
> 
> 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.

That's interesting. Do you have any specific examples?

> At runtime, C++ exceptions and Objective-C 
> exception can't mix unless you require Objective-C 2.0, Leopard, and
compile for 
> 64 bits (if I recall correctly), which makes error handling in
Objective-C++ 
> tedious in the best case and extremely error prone in the worst case.

You're correct that they are unified in the 64-bit runtime but not 
otherwise. However I'm not sure how much this really matters. Exceptions 
are so rarely used it Cocoa code that being unable to mix them never bit 
me; most of the time, if an ObjC exception is being thrown then it's 
either on your computer and should be caught by the debugger, or it's on 
the user's computer and it's pretty much game over anyway.

I did work on a fairly sizable Objective-C++ project for a couple of years

and for the most part it went well, but I enforced a very strict 
separation between the two with the exception of just a few places where 
they met up to exchange information, and the C++ component was designed to

be ****table to some very restricted platforms and so didn't use a lot of 
advaced C++ features. I'm sure you have more experience with this than I 
do.

-- 
Michael Ash
Rogue Amoeba Software