summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Language/ObjC/CF.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Change Target::EvaluateExpression to take an ExecutionContextScope * rather ↵Jim Ingham2015-10-281-0/+1
| | | | | | | | | | | | | | | | than a StackFrame * (StackFrame is an ExecutionContextScope.) That allows you to call an expression on a particular Thread, but not using the context of any particular frame. That in turn is useful for injecting utility functions that don't actually depend on locals/self/etc of the current frame. I also had to include StackFrame.h in a couple of places so the compiler knew how to downcast StackFrame to ExecutionContextScope. <rdar://problem/22852953> llvm-svn: 251564
* This is the work I was building up to with my patches yesterdayEnrico Granata2015-10-071-6/+41
| | | | | | | | | Introduce the notion of Language-based formatter prefix/suffix This is meant for languages that share certain data types but present them in syntatically different ways, such that LLDB can now have language-based awareness of which of the syntax variations it has to present to the user when formatting those values This is goodness for new languages and interoperability, but is NFC for existing languages. As such, existing tests cover this llvm-svn: 249587
* Move Objective-C data formatters to the Objective-C language plugin where ↵Enrico Granata2015-09-141-0/+298
they belong llvm-svn: 247627
OpenPOWER on IntegriCloud