Re: Cross-Platform Windows plus Mac

In article <1193352778.605816@[EMAIL PROTECTED]
>,
 Michael Ash <mike@[EMAIL PROTECTED]
> wrote:

> 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?

I've long since stopped caring. I filed my Radar bugs, declared Obj-C++
not 
worth my time, and moved on. I'm sure I could dig them up if I really
cared, but 
I don't.

> 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.

If you treat C++ as better C, and ignore all the advanced... features...
then 
you can probably get pretty far with Objective-C++. It may very well be a
useful 
tool for a lot of people, I just think it bears mentioning that it's not
exactly 
a magic wand that you can wave over your C++ code to make a Cocoa app
around it 
(which is how it's often presented).

Ben

-- 
If this message helped you, consider buying an item
from my wish list: <http://artins.org/ben/wishlist>

I changed my name: <http://periodic-kingdom.org/People/NameChange.php>