[Python-checkins] python/dist/src/Misc SpecialBuilds.txt,1.11,1.12

mwh@users.sourceforge.net mwh@users.sourceforge.net
Tue, 30 Jul 2002 08:25:59 -0700


Update of /cvsroot/python/python/dist/src/Misc
In directory usw-pr-cvs1:/tmp/cvs-serv23562

Modified Files:
	SpecialBuilds.txt 
Log Message:
Repair fill-paragraph damage.

Clarify LLTRACE description.  It was introduced in 1992, revision 2.20 of
ceval.c, well before Python 1.0!


Index: SpecialBuilds.txt
===================================================================
RCS file: /cvsroot/python/python/dist/src/Misc/SpecialBuilds.txt,v
retrieving revision 1.11
retrieving revision 1.12
diff -C2 -d -r1.11 -r1.12
*** SpecialBuilds.txt	30 Jul 2002 09:49:29 -0000	1.11
--- SpecialBuilds.txt	30 Jul 2002 15:25:57 -0000	1.12
***************
*** 142,146 ****
  blocks.
  ---------------------------------------------------------------------------
! COUNT_ALLOCS introduced in 0.9.9 partly broken in 2.2 and 2.2.1
  
  Each type object grows three new members:
--- 142,147 ----
  blocks.
  ---------------------------------------------------------------------------
! COUNT_ALLOCS                                            introduced in 0.9.9
!                                              partly broken in 2.2 and 2.2.1
  
  Each type object grows three new members:
***************
*** 187,200 ****
      most recently is at the front of the list.
  ---------------------------------------------------------------------------
! LLTRACE                                    introduced ...?  Long time ago!
  
! Compile in support of Low Level TRACE-ing of the man interpreter loop.
  
  When this preprocessor symbol is defined, before eval_frame
! (eval_code2 before 2.2) executes a frame's code checks its global
! namespace for a variable "__lltrace__".  If such a variable is found,
! mounds of information about what the interpreter is doing are sprayed
! to stdout, such as every opcode and opcode argument and values pushed
! onto and popped off the value stack.
  
  Not useful very often, but very useful when needed.
--- 188,201 ----
      most recently is at the front of the list.
  ---------------------------------------------------------------------------
! LLTRACE                                          introduced well before 1.0
  
! Compile in support of Low Level TRACE-ing of the main interpreter loop.
  
  When this preprocessor symbol is defined, before eval_frame
! (eval_code2 before 2.2) executes a frame's code it checks the frame's
! global namespace for a variable "__lltrace__".  If such a variable is
! found, mounds of information about what the interpreter is doing are
! sprayed to stdout, such as every opcode and opcode argument and values
! pushed onto and popped off the value stack.
  
  Not useful very often, but very useful when needed.