ScriptInterpreters are about providing a way to script lldb. The REPL in lldb is about giving users an interactive way to play with a compiled language with no requirement that it bind to lldb in particular.
The two seem fairly different concepts. Jim > On Mar 21, 2017, at 6:44 PM, Zachary Turner via lldb-dev > <lldb-dev@lists.llvm.org> wrote: > > Not having written or debugged swift before, what does it give you that a > ScriptInterpreter plugin doesn't? It seems like ScriptInterpreterPython is, > in fact, just a kind of REPL, albeit one that interacts with the debugger > itself rather a particular target. I'm wondering if anyone who wanted this > kind of thing in the future could just do it as a ScriptInterpreter plugin > On Tue, Mar 21, 2017 at 6:37 PM Jason Molenda <jmole...@apple.com> wrote: > I don't follow REPL issues very closely but I think some people may have > hopes of doing a repl in a language other than swift in the future which is > why it was upstreamed to llvm. > > J > > > On Mar 21, 2017, at 6:34 PM, Zachary Turner <ztur...@google.com> wrote: > > > > Thanks, I had a suspicion it might be used in Swift. Given that swift > > seems to be the only consumer, and there are no plans for support for any > > other languages, would it be reasonable to say that it's a swift-specific > > addition and could be in the swift repo? > > > > If not, I will need to come up with a good way to get REPL.h to not > > #include code from the source tree (and ideally, not #include code from > > Commands at all). > > > > On Tue, Mar 21, 2017 at 6:24 PM Jason Molenda <jmole...@apple.com> wrote: > > It's used in the swift lldb, https://github.com/apple/swift-lldb > > > > The idea is to have any non-swift specific code in llvm.org; the github > > repository for swift specific additions. > > > > > > > On Mar 21, 2017, at 6:19 PM, Zachary Turner via lldb-dev > > > <lldb-dev@lists.llvm.org> wrote: > > > > > > AFAICT this is all dead code. Unless someone is using it out of tree? > > > There is a way to register repl support for various languages, but no > > > code in tree is actually doing this. It's possible I'm just not finding > > > the code though. > > > > > > It appears this code was all added about 18 months ago, and if it hasn't > > > found any use in that time frame, it would be great to remove it to > > > reduce technical debt. > > > > > > That said, if it's actually being used in tree somewhere and I'm just > > > overlooking it, let me know. > > > _______________________________________________ > > > lldb-dev mailing list > > > lldb-dev@lists.llvm.org > > > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > > > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
