ghost at cs.msu.su
Wed Sep 8 14:38:02 UTC 2010
On Wednesday 08 September 2010 18:29:58 David Nolden wrote:
> 2010/9/8 Vladimir Prus <ghost at cs.msu.su>:
> > In fact, when you are wondering why 'result', or any other variable, has the
> > value it has, you should really know what type it has, where it is defined,
> > and what should it contain. In most debugging cases, you have quite local
> > context, and where a local context is not sufficient, you better have some
> > global understanding of the code -- for example achieved through browising
> > the code in the "Code" area.
> That may be true if you're debugging code that you've written by
> yourself. However debugging can also be used to "learn" how specific
> code works, for example to see what code paths are used on a specific
> action, without having to instantly fully understand a huge new
> codebase. In such a situation, both tooltips would be useful.
Even then, a value tooltip is useful every single time a given line
of code is executed. context tooltip will soon become less and less
useful. And if both tooltips are shown by default, and then context
tooltip is disabled with the "x" button -- you won't get context
tooltip for a variable you never saw before.
More information about the KDevelop-devel