The frame variable command can handle mistaken use of . for ->, and vice versa,
but up until now it has been an error when the user makes such a mistake. This change
adds a flag to frame variable which allows these mistakes to be fixed. The idea is why
make the user manually edit the command if lldb can figure it out.
This is similar to expression which supports fixits supplied by the compiler, which
include correcting . to ->, and vice versa.
Unlike expression, there is no diagnostic message to draw attention to the fix. The
fixed expression _is_ printed though. Compare:
(lldb) frame var -X on thing->field (int) thing.field = 30
to
(lldb) expr thing->field (int) $0 = 30 Fix-it applied, fixed expression was: thing.field
I wasn't sure it was worth the noise, so I went with the simple approach.