[Lldb-commits] [PATCH] D11482: Add target setting to have the language follow the frame's CU.

Dawn Perchik dawn+llvm at burble.org
Tue Jul 28 21:36:43 PDT 2015

dawn added a comment.

On Mon, Jul 27, 2015 at 11:24:01AM -0700, Jim Ingham wrote:

> Just to be clear...  Sean doesn't have a DESIRE to have the expression parser use ObjC++ anytime the language is a C family language.  Rather he MUST right now, because the expression parser uses features of C++ to capture values.  We could switch to using C++ in C/C++ situations, and ObjC++ in others, but there wasn't sufficient motivation to add that.  Sometime when we get some spare cycles we'll try to relax the need for C++, and then we'll truly be able to follow the frame language.  For now, we do "Want C -> get ObjC++", "Want ObjC -> get ObjC++" etc...  But again, that is not a fundamental choice, it is an implementation necessity.

I see.  This is a major pain for Pascal however, because C++ and ObjC/ObjC++ conflict directly with Pascal, so unless the user specifies the language (via target.language or expr --language), they can't evaluate at all.  So until you guys can find those "spare cycles", we're forced to maintain private patches.



More information about the lldb-commits mailing list