Re: C++ exception results in SIGABRT
Re: C++ exception results in SIGABRT
- Subject: Re: C++ exception results in SIGABRT
- From: Chris Espinosa <email@hidden>
- Date: Tue, 19 Feb 2008 11:15:54 -0700
On Feb 19, 2008, at 10:59 AM, Stefan Werner <email@hidden> wrote:
On Feb 19, 2008, at 6:21 PM, Chris Espinosa wrote:
For mixed C and C++ code, the default item is present, but performs
the default action in both languages, that is, leaves exceptions
enabled in C++ but ignores them in C. Which is not what you
desire, no. The solution is to explicitly check Enable C++
Exceptions at the target level, rather than leaving it enabled by
default. That way you get the consistent explicit behavior (-
fexceptions) for both C and C++ code, rather than the inconsistent
default behavior.
To make sure I understand this corretly: checking "Enable C++
Exceptions" on Target level does not give the same result as the
target inheriting it from project or xcconfig level? So whether or
not I set GCC_ENABLE_CPP_EXCEPTIONS = YES in my xcconfig has no
effect whatsoever?
Defining it explicitly in your .xcconfig should behave as desired; if
it doesn't, please write up a bug report.
The behavior I would expect from the checkbox is that checking it
would (as the help text suggests) explicitly enable C++ exceptions
for C code (-fexceptions) and unchecking it woudl explicitly disable
it (-fno-exceptions).
That's all correct. The deceptive part is that the default state is
*checked but undefined*. Which gives the correct default behavior in C+
+ but the undesired behavior in C.
The point is that checked-but-not-bold behaves differently than bold-
and-checked, at either target I'd project level.
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden