It isn't technically necessary, but on OS X it is very common for people to want to examine global app state from wherever and that is always ObjC, so we'd tick off our users if we forced them to explicitly dial up ObjC in other contexts. For other platforms it would be fine to choose just C++. And if the user explicitly dials up C++ (by passing --language) it should be fine to not add ObjC. But if we're setting it automatically on OS X there's a pretty strong expectation that you can just run an expression and ObjC types will be available.
Jim > On Sep 3, 2015, at 7:08 PM, Dawn Perchik <dawn+l...@burble.org> wrote: > > dawn added a comment. > > In http://reviews.llvm.org/D11102#234730, @spyffe wrote: > >> I want to follow up and make non-Apple platforms not force ObjC (it doesn't >> matter for making the expression parser work). > > > Hi Sean, > > I have one question about this that still bugs me... I understand that C++ > is needed in C and ObjC because of implementation details of expression > evaluation, but why is ObjC needed for C++? > > It will be awesome if/when you can follow up on this and remove this > requirement. Let me know when that's done and I'll remove the workarounds > that force ObjC and give it a try. > > Thanks! > > > Repository: > rL LLVM > > http://reviews.llvm.org/D11102 > > > _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
