You cannot throw C++ exceptions across Objective-C functions. If you want to
catch this exception, you will have to catch it in drawRect, and decide
there what to do with it.
The earlier emails seem to mention that for 64bit apps this will not
be a problem. Is that the case or did I
The earlier emails seem to mention that for 64bit apps this will not
be a problem. Is that the case or did I misunderstand them?
You understood correctly. The restriction I described is for 32-bit apps.
--
Scott Ribe
[EMAIL PROTECTED]
http://www.killerbytes.com/
(303) 722-0567 voice
On 05.07.2008, at 17:01, Jim Crafton wrote:
You cannot throw C++ exceptions across Objective-C functions. If
you want to
catch this exception, you will have to catch it in drawRect, and
decide
there what to do with it.
The earlier emails seem to mention that for 64bit apps this will not
be
On Sat, Jul 5, 2008 at 10:11 AM, Uli Kusterer
[EMAIL PROTECTED] wrote:
On 05.07.2008, at 17:01, Jim Crafton wrote:
You cannot throw C++ exceptions across Objective-C functions. If you want
to
catch this exception, you will have to catch it in drawRect, and decide
there what to do with it.
On 05.07.2008, at 19:52, Clark Cox wrote:
If C++ code behaves oddly in the presence of unknown exceptions, then
that C++ code is broken. :)
Isn't that how code always is? ;-)
Cheers,
-- Uli Kusterer
The Witnesses of TeachText are everywhere...
http://www.zathras.de
I have found stuff on the internet about issues with throwing C++
exceptions, and I've run into something which I think is what these
articles are talking about but I'm not 100% sure so I thought I'd ask.
I have some C+ code that is being called as a result of the AppKit
framework updating a view
In the 32 bit [legacy] Mac OS X runtime, C++ and Objective-C
exceptions Do Not Mix. Oil water. C++ exceptions are ignored by
@try/@catch and vice-versa.
In the modern runtime (64 bit Mac OS X elsewhere), the exception
model has been unified. Not only are C++ and Objective-C
I'm developing this on 10.5, Xcode 3.0. Is that considered the newer
version, or is there an Xcode setting that I need to explicitly adjust
for this?
On Fri, Jul 4, 2008 at 3:45 PM, Bill Bumgarner [EMAIL PROTECTED] wrote:
In the 32 bit [legacy] Mac OS X runtime, C++ and Objective-C exceptions Do
On 04.07.2008, at 22:03, Jim Crafton wrote:
I'm developing this on 10.5, Xcode 3.0. Is that considered the newer
version, or is there an Xcode setting that I need to explicitly adjust
for this?
64-bit is the sticking point. If you build for 64-bit, they're
unified, but Apple can't change
64-bit is the sticking point. If you build for 64-bit, they're unified, but
Apple can't change the 32-bit runtime on the Mac for compatibility reasons.
So the switch would be setting the architecture to 64-bit and removing the
32-bit architecture. But of course then your app won't run on Macs
In the C++ code I throw an exception. Outside of this, several steps
down the stack frame, I have a C++ function that has a try catch
You cannot throw C++ exceptions across Objective-C functions. If you want to
catch this exception, you will have to catch it in drawRect, and decide
there what
11 matches
Mail list logo
