Re: [PATCH v4] Make chained function calls in expressions work

[Siva Chandra <sivachandra@google.com>]

On Tue, Nov 11, 2014 at 7:21 AM, Ulrich Weigand <uweigand@de.ibm.com> wrote:
> No, please go ahead and ask questions; it's always better to hash the
> main direction out before spending a lot of time on implementating
> something ...  :-)

This time I am really done :)

Thanks for taking time to explain things to me. I am just putting down
my point of view as to why I am still looking for the correct
approach, and after all your explanations, I am now convinced that the
thread approach is the best. One other place where chained function
calls can happen is in Python for example. If val1, val2 and val3 are
gdb.Value objects of type std::string, and if we have val1 + val2 in
Python code, then overloaded operator+ is invoked. However, if we have
val1 + val2 + val3, it will fail currently as this is also a chained
function call. We could perhaps do the 'setup' and 'cleanup' in
ensure_python_env as well (just as we want to do in
evaluate_expression or evaluate_subexp). I do not want to hold up the
current work in relation to this. We can discuss this probably as a
separate topic.