> On Dec 10, 2019, at 3:11 AM, Pavel Labath via lldb-dev
> wrote:
>
> On 09/12/2019 18:27, Jonas Devlieghere wrote:
>> On Mon, Dec 9, 2019 at 1:55 AM Pavel Labath wrote:
>>>
>>> I think this would be a very interesting project, and would allow us to
>>> flesh out the details of the script in
On 09/12/2019 18:27, Jonas Devlieghere wrote:
> On Mon, Dec 9, 2019 at 1:55 AM Pavel Labath wrote:
>>
>> I think this would be a very interesting project, and would allow us to
>> flesh out the details of the script interpreter interface.
>>
>> A lot of the complexity in our python code comes from
Given that the response so far has been positive, I've put up the
patches for review:
https://reviews.llvm.org/D71232
https://reviews.llvm.org/D71234
https://reviews.llvm.org/D71235
Jonas
On Mon, Dec 9, 2019 at 9:27 AM Jonas Devlieghere wrote:
>
> On Mon, Dec 9, 2019 at 1:55 AM Pavel Labath wr
On Mon, Dec 9, 2019 at 1:55 AM Pavel Labath wrote:
>
> I think this would be a very interesting project, and would allow us to
> flesh out the details of the script interpreter interface.
>
> A lot of the complexity in our python code comes from the fact that
> python can be (a) embedded into lldb
Python is in general a no-go for a BSD basesystem (micropython can be an
exception.. but Python is so large today that we can reevaluate this
statement at some point). This is why we need to either disable certain
features in LLDB or split LLDB between everything without Python in the
base and the
I think this would be a very interesting project, and would allow us to
flesh out the details of the script interpreter interface.
A lot of the complexity in our python code comes from the fact that
python can be (a) embedded into lldb and (b) lldb can be embedded into
python. It's been a while si
I think this is great, thanks for working on this! My only concern is that I
would prefer if we could limit the Lua tests to just the Lua->C++ calling
machinery (e.g., that we handle Lua strings correctly and all that jazz) and
not fragment our test suit. Otherwise Lua seems to require far less
Hi everyone,
Earlier this year, when I was working on the Python script
interpreter, I thought it would be interesting to see what it would
take to support other scripting languages in LLDB. Lua, being designed
to be embedded, quickly came to mind. The idea remained in the back of
my head, but I n
