[Psyco-checkins] CVS: psyco/doc psycoguide.tex,1.6,1.7

[Armin R. <ar...@us...>]

Update of /cvsroot/psyco/psyco/doc
In directory sc8-pr-cvs1:/tmp/cvs-serv15271/doc

Modified Files:
	psycoguide.tex 
Log Message:
string concatenation revisited (now loops of s+=t should finally be fast)

Index: psycoguide.tex
===================================================================
RCS file: /cvsroot/psyco/psyco/doc/psycoguide.tex,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** psycoguide.tex	2 May 2003 13:36:48 -0000	1.6
--- psycoguide.tex	11 Jun 2003 17:33:27 -0000	1.7
***************
*** 10,16 ****
  }
  
! \date{May 2, 2003}
  
! \release{1.0}                   % release version
  
  \makeindex
--- 10,16 ----
  }
  
! \date{June 5, 2003}
  
! \release{1.1}                   % release version
  
  \makeindex
***************
*** 868,877 ****
  \item the \code{exec} statement --- in some cases you can use \function{eval} and/or \function{compile} instead, under the restrictions described in section \ref{patchedfunctions}
  
! \item class definitions (all the code immediately within a \code{class} statement)
  
  \item functions with free or cell vars, which occur with Python's new nested scopes (as enabled by \samp{from __future__ import nested_scopes}); this concerns both the function whose local variable is made visible to a subfunction, and the subfunction using such a local variable
  
- \item miscellaneous places where Python's bytecode compiler cannot optimize the local variables, most notably at the top-level of the modules (i.e.\ outsite any function)
- 
  \item generators
  
--- 868,875 ----
  \item the \code{exec} statement --- in some cases you can use \function{eval} and/or \function{compile} instead, under the restrictions described in section \ref{patchedfunctions}
  
! \item top-level module code and the code defining a class\footnote{The methods themselves are fine; this only concerns the code that runs in order to define the class (generally only a bunch of \code{def} statements)} --- this is because Python's compiler can emit fast-variable-access bytecode only for function definitions
  
  \item functions with free or cell vars, which occur with Python's new nested scopes (as enabled by \samp{from __future__ import nested_scopes}); this concerns both the function whose local variable is made visible to a subfunction, and the subfunction using such a local variable
  
  \item generators
  
***************
*** 884,891 ****
    \lineiii{ 84}{\code{IMPORT_STAR  }}{\code{from xx import *}}
    \lineiii{ 85}{\code{EXEC_STMT    }}{\code{exec xx}}
!   \lineiii{ 86}{\code{YIELD_VALUE  }}{generators' \code{yield xx}}
!   \lineiii{ 90}{\code{STORE_NAME   }}{non-optimizable scopes (e.g.\ at module top-level)}
!   \lineiii{ 91}{\code{DELETE_NAME  }}{non-optimizable scopes (e.g.\ at module top-level)}
!   \lineiii{101}{\code{LOAD_NAME    }}{non-optimizable scopes (e.g.\ at module top-level)}
    \lineiii{134}{\code{MAKE_CLOSURE }}{nested scopes}
    \lineiii{135}{\code{LOAD_CLOSURE }}{nested scopes}
--- 882,889 ----
    \lineiii{ 84}{\code{IMPORT_STAR  }}{\code{from xx import *}}
    \lineiii{ 85}{\code{EXEC_STMT    }}{\code{exec xx}}
!   \lineiii{ 86}{\code{YIELD_VALUE  }}{generators}
!   \lineiii{ 90}{\code{STORE_NAME   }}{(1)}
!   \lineiii{ 91}{\code{DELETE_NAME  }}{(1)}
!   \lineiii{101}{\code{LOAD_NAME    }}{(1)}
    \lineiii{134}{\code{MAKE_CLOSURE }}{nested scopes}
    \lineiii{135}{\code{LOAD_CLOSURE }}{nested scopes}
***************
*** 893,896 ****
--- 891,896 ----
    \lineiii{137}{\code{STORE_DEREF  }}{nested scopes}
  \end{tableiii}
+ 
+ (1): these appear outside functions, like at the module top-level or in the body defining a class.  They can sometimes appear in a function too, e.g.\ when the function uses \code{from xx import *} or \code{exec xx}.