• Alexandre Vassalotti's avatar
    Merged revisions 72487-72488,72879 via svnmerge from · 7b82b40a
    Alexandre Vassalotti yazdı
    svn+ssh://pythondev@svn.python.org/python/trunk
    
    ........
      r72487 | jeffrey.yasskin | 2009-05-08 17:51:06 -0400 (Fri, 08 May 2009) | 7 lines
    
      PyCode_NewEmpty:
      Most uses of PyCode_New found by http://www.google.com/codesearch?q=PyCode_New
      are trying to build an empty code object, usually to put it in a dummy frame
      object. This patch adds a PyCode_NewEmpty wrapper which lets the user specify
      just the filename, function name, and first line number, instead of also
      requiring lots of code internals.
    ........
      r72488 | jeffrey.yasskin | 2009-05-08 18:23:21 -0400 (Fri, 08 May 2009) | 13 lines
    
      Issue 5954, PyFrame_GetLineNumber:
      Most uses of PyCode_Addr2Line
      (http://www.google.com/codesearch?q=PyCode_Addr2Line) are just trying to get
      the line number of a specified frame, but there's no way to do that directly.
      Forcing people to go through the code object makes them know more about the
      guts of the interpreter than they should need.
    
      The remaining uses of PyCode_Addr2Line seem to be getting the line from a
      traceback (for example,
      http://www.google.com/codesearch/p?hl=en#u_9_nDrchrw/pygame-1.7.1release/src/base.c&q=PyCode_Addr2Line),
      which is replaced by the tb_lineno field.  So we may be able to deprecate
      PyCode_Addr2Line entirely for external use.
    ........
      r72879 | jeffrey.yasskin | 2009-05-23 19:23:01 -0400 (Sat, 23 May 2009) | 14 lines
    
      Issue #6042:
      lnotab-based tracing is very complicated and isn't documented very well.  There
      were at least 3 comment blocks purporting to document co_lnotab, and none did a
      very good job. This patch unifies them into Objects/lnotab_notes.txt which
      tries to completely capture the current state of affairs.
    
      I also discovered that we've attached 2 layers of patches to the basic tracing
      scheme. The first layer avoids jumping to instructions that don't start a line,
      to avoid problems in if statements and while loops.  The second layer
      discovered that jumps backward do need to trace at instructions that don't
      start a line, so it added extra lnotab entries for 'while' and 'for' loops, and
      added a special case for backward jumps within the same line. I replaced these
      patches by just treating forward and backward jumps differently.
    ........
    7b82b40a
lnotab_notes.txt 5.26 KB