<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>While digging around on the web to figure out what should be perfectly valid ObjC+ blocks code wouldn't compile on llvm-gcc 4.2, I ran into the following comment on the quality of the ObjC++ support. Questions:</div><div><br></div><div>1) Was this characterization valid? </div><div>2) Is this characterization of ObjC++ true with the current clang/llvm implementation?</div><div><br></div><div><br></div><div><br></div><div><blockquote type="cite"><p style="margin: 0px 0px 1em; padding: 0px; border: 0px; font-size: 14px; vertical-align: baseline; background-color: rgb(255, 255, 255); clear: both; word-wrap: break-word; font-family: Arial, 'Liberation Sans', 'DejaVu Sans', sans-serif; line-height: 18px; text-align: left; position: static; z-index: auto; "><soapbox>I recommend avoiding Objective-C++ as much as possible. It's slow to compile, bloated to run (particularly with ARC since it turns on <a href="http://clang.llvm.org/docs/AutomaticReferenceCounting.html" rel="nofollow" style="margin: 0px; padding: 0px; border: 0px; vertical-align: baseline; color: rgb(74, 107, 130); text-decoration: none; cursor: pointer; ">-fobjc-arc-exceptions</a>), buggy in the compiler and the debugger, and mostly a mess in my experience giving the worst of both worlds. C++ is fine. Objective-C is fine. Just keep the interface between them as small as possible. </soapbox></p></blockquote></div><div><a href="http://stackoverflow.com/questions/7031540/variable-is-not-a-static-member-of-class">http://stackoverflow.com/questions/7031540/variable-is-not-a-static-member-of-class</a></div><div><br></div><div><br></div></body></html>