Re: Cross-Platform Windows plus Mac

In comp.sys.mac.programmer.help Gabriele Greco
<gabrielegreco@[EMAIL PROTECTED]
> wrote:
> Michael Ash wrote:
> 
>> 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.
> 
> You speak from the wrong point of view.
> 
> Image that you have a 1.500.000 code project and only 5% is the GUI 
> related code.
> 
> Your code uses exceptions, like many modern C++ projct do. Obviously 
> you'll need to pass exceptions to your GUI level if something is wrong.
> 
> You want to write a Mac version of your project and you really want to 
> make it a real mac app, but you cannot rewrote half of the project to do

> so, so you'll end up using QT or wxWidgets...
> 
> This is a real world scenario.

I have no idea why you think this is incompatible with the idea that you 
lose if you throw an *Objective-C* exception. In fact it sounds like 
you're in 100% violent agreement with me, all except for the part where 
you say I'm wrong.

>> 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.
> 
> Actually you can write "advanced" c++ and be compatible with OSX, Win32,

> Linux. Only the GUI level it's a problem and mostly on OSX cause on 
> win32 and linux the interfaces are so standardless that no one cares if 
> your application is slightly different from what they are used to :)

Well of course. The "very restriction platforms" I'm talking about are, of

course, *not* among OS X, Win32, and Linux.

-- 
Michael Ash
Rogue Amoeba Software