On Aug 25, 2012, at 4:12 AM, Jonathan Schleifer wrote: > Am 25.08.2012 um 12:54 schrieb David Chisnall: >> It is impossible to use exceptions with ObjC++ without those - the old GCC >> exception model is a mess. If you want to support ObjC++ exceptions, >> implement those symbols. > > Well, I'm not planing to use C++'s catch to catch exceptions thrown using > ObjC's @throw or ObjC's @try when thrown using C++'s throw. I'm just going to > have the two exception models working separately. This should work by just > emitting ObjC exceptions the same way in ObjC++ as in ObjC and C++ exceptions > the same as in C++ sources. Or did I miss something?
Is there a particular reason why you don't want the exception models to interact correctly? It's quite straightforward to make it work when you've designed things properly. John. _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
