jimingham wrote: The counter to this is that `dwim-print` differs from `frame var` in that it supports complex expressions. So having it work for simple statements of a variable name (what frame var and target var already do just fine) but then fail when the SAME name is used in a slightly more complicated expression is a serious failure to do its particular job.
Jim > On Mar 15, 2024, at 2:28 PM, Dave Lee ***@***.***> wrote: > > > I'll change this to scope lookup of persistent variables to the expected > language. > > However, there's an argument to be made that dwim-print $my_var should work > anywhere. I think that follows the spirit of "do what I mean". Maybe in the > future I'll propose that in a separate change. > > — > Reply to this email directly, view it on GitHub > <https://github.com/llvm/llvm-project/pull/85152#issuecomment-2000462325>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ADUPVWZKCVFMQ7535FPIMULYYNRYRAVCNFSM6AAAAABEVCQEZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBQGQ3DEMZSGU>. > You are receiving this because you are on a team that was mentioned. > https://github.com/llvm/llvm-project/pull/85152 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
