Closed GoogleCodeExporter closed 9 years ago
The debugger hint just evaluates the word under the cursor in the context of
the current stack frame.
As per your instructions if you go to the Call Stack Window and select the top
frame (last in the list) and hover again the cursor over 'n' (any 'n') you will
see the value as "Hello".
So debugger hints do not do any scope analysis and in any case it would be very
difficult to associate reliably different scopes with currently executing stack
frames.
I understand the confusion in the minds of the students but I think that at
some point they need to understand the concept of stack frames (Call stack
window) and how they may or may not relate to code scopes.
Original comment by pyscripter
on 16 Aug 2012 at 10:32
Original issue reported on code.google.com by
cspwc...@gmail.com
on 28 Jul 2012 at 10:59