• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode Release vs Debug Differences: Problem with Exception Types
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode Release vs Debug Differences: Problem with Exception Types


  • Subject: Re: Xcode Release vs Debug Differences: Problem with Exception Types
  • From: Chris Hanson <email@hidden>
  • Date: Tue, 17 Jun 2008 18:33:20 -0700

On Jun 17, 2008, at 12:13 PM, Marshall Clow wrote:

At 12:55 PM -0600 6/17/08, Matthew Tobiasz wrote:
I've reproduced this issue in a completely new project, started from scratch. Here's exactly what I did.

[ snip ]

I suspect that you've run into a really ugly "feature" of gcc.

Actually, it's a feature of the C++ specification, and not one that's likely to be resolved any time soon.


The issue is this: Different compilers and runtimes can and do interpret the One Definition Rule differently.

In the specific case Matthew is running into, the GCC C++ runtime compares type information -- for example, in a "catch ()" construct -- based on the address of its typeinfo structure. Microsoft Visual C++, on the other hand, compares the same type information based on the name in its typeinfo structure.

GCC's interpretation could be argued to be more correct: For example, if you have two libraries each with its own definition of FooException, GCC's C++ runtime won't mistakenly interpret one FooException as the other in a "catch ()" construct. On the other hand, with GCC you have to be more pedantic about ensuring type information for classes defined in a shared/dynamic library is exported properly.

The last time I heard several C++ standards committee members talk about it (C++ Live, November 2005), Bjarne Stroustrup himself stated that the behavior of C++ when using shared/dynamic libraries was something better left to the market (e.g. implementors) rather than the standards committee.

I'll second Marshall's recommendation to read TN 2185 <http://developer.apple.com/technotes/tn2007/tn2185.html > to get more detail on this.

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


  • Follow-Ups:
    • Re: Xcode Release vs Debug Differences: Problem with Exception Types
      • From: Marshall Clow <email@hidden>
References: 
 >Xcode Release vs Debug Differences: Problem with Exception Types (From: Matthew Tobiasz <email@hidden>)
 >Re: Xcode Release vs Debug Differences: Problem with Exception Types (From: Matthew Tobiasz <email@hidden>)
 >Re: Xcode Release vs Debug Differences: Problem with Exception Types (From: Matthew Tobiasz <email@hidden>)
 >Re: Xcode Release vs Debug Differences: Problem with Exception Types (From: Marshall Clow <email@hidden>)

  • Prev by Date: dllimport, dllexport attributes
  • Next by Date: Re: Equivalent to xcconfig conditionals available?
  • Previous by thread: Re: Xcode Release vs Debug Differences: Problem with Exception Types
  • Next by thread: Re: Xcode Release vs Debug Differences: Problem with Exception Types
  • Index(es):
    • Date
    • Thread