[Lldb-commits] [PATCH] D11790: Fix ObjC++ types Class and id being defined in C and C++ expressions.

[Paul Herman via lldb-commits]

paulherman added a comment.

The idea is that, as I user, I do not expect the identifiers "Class" and "id" to not be available - I don't think I've seen a warning or notice about that when evaluating expressions.

I believe that setting the language based on the current frame is a good guess. I think evaluating something in the language of the current frame is more common than evaluating something that is in ObjC++ and the current frame is C++.

The idea about target-level language is that it only selects a specific language (i.e. not the default ObjC++) if all the compile units are in the same language. I believe this to be right since a debugger is not a REPL, hence we shouldn't expect the users to evaluate something in ObjC++ if their binary doesn't contain anything related to that language.


http://reviews.llvm.org/D11790