Re: determining the type of a variable in CL

s> unfamiliar codebase. This method takes a handful of parameters that I
s> now have to trace back to the original calling method in order to find
s> out what they actually are. Or do I?
s> In statically-typed languages its easy to find out more about the
s> types in use in a specific context (function or method) because of the
s> declarations.

and in dynamic-typed languages it is easy to find out more about the types
in use in specific context .. in runtime.

there are plenty of ways to do inspection, as other people pointed out.

but i wonder what stopped you from inserting PRINTs in the function of
interest and see what parameters are. isn't that obvious?


.

Relevant Pages

  • Re: [patch 04/18] x86, bts: wait until traced task has been scheduled out
    ... If the traced task is running, the cpu might still ... trace that task after the branch trace control bits have cleared. ... Wait until the traced task has been scheduled out before ... A similar problem affects the task debug store context. ...
    (Linux-Kernel)
  • Re: [PATCH 2/2] tracing/events/lockdep: move tracepoints within recursive protection
    ... it allows one event to trace within another event. ... But surely not in the same context. ... You could do a 4 level recursion ... Why not allow a nested interrupt to trace? ...
    (Linux-Kernel)
  • Re: Tcl bug?
    ... being substituted in the context of TraceOP. ... you can get really misleading error messages from ... The error message and the error context ... I guess since the trace command had triggered the callback, a procedure was running and so the scope was local. ...
    (comp.lang.tcl)
  • Re: Mass and strong interaction.
    ... > In this context, it's of interest to note that for the Leptons, the ... > trace Trof the mass matrix M_L is, to a high degree of accuracy, ...
    (sci.physics.research)
Loading