summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJim Ingham <jingham@apple.com>2017-06-01 01:05:30 +0000
committerJim Ingham <jingham@apple.com>2017-06-01 01:05:30 +0000
commitab194a26da64f372eeb0becbcf2264860ff9135e (patch)
treeab950116434cb14a0cefe6c38cd0421c915ced30
parent6b41141863bc04daa13bc0e958df616bd0827993 (diff)
downloadbcm5719-llvm-ab194a26da64f372eeb0becbcf2264860ff9135e.tar.gz
bcm5719-llvm-ab194a26da64f372eeb0becbcf2264860ff9135e.zip
Forgot to mention rewriting CommandObject::DoExecute
using the SB API's not the lldb_private API's. llvm-svn: 304379
-rwxr-xr-xlldb/www/projects.html19
1 files changed, 19 insertions, 0 deletions
diff --git a/lldb/www/projects.html b/lldb/www/projects.html
index b1aeb1021ec..e375eb9cc3d 100755
--- a/lldb/www/projects.html
+++ b/lldb/www/projects.html
@@ -244,6 +244,25 @@
</li>
<li>
+ Reimplement the command interpreter commands using the SB API
+ <p>
+ Currently, all the CommandObject::DoExecute methods are implemented
+ using the lldb_private API's. That generally means that there's code
+ that gets duplicated between the CommandObject and the SB API that does
+ roughly the same thing. We would reduce this code duplication, present a
+ single coherent face to the users of lldb, and keep
+ ourselves more honest about what we need in the SB API's if we implemented
+ the CommandObjects::DoExecute methods using the SB API's.
+ </p>
+ <p>
+ BTW, it is only the way it was much easier to develop lldb if it had a functioning
+ command-line early on. So we did that first, and developed the SB API's when lldb
+ was more mature. There's no good technical reason to have the commands use the
+ lldb_private API's.
+ </p>
+ </li>
+
+ <li>
Documentation and better examples
<p>
OpenPOWER on IntegriCloud