[Python-checkins] CVS: python/dist/src/Doc/ext ext.tex,1.77,1.78
Fred L. Drake
python-dev@python.org
Fri, 30 Jun 2000 10:58:36 -0700
Update of /cvsroot/python/python/dist/src/Doc/ext
In directory slayer.i.sourceforge.net:/tmp/cvs-serv11830/ext
Modified Files:
ext.tex
Log Message:
Small grammatical correction from Frank Stajano. Added comment with
suggestion from Frank for an example and further explanation.
Index: ext.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/ext/ext.tex,v
retrieving revision 1.77
retrieving revision 1.78
diff -C2 -r1.77 -r1.78
*** ext.tex 2000/06/28 16:15:08 1.77
--- ext.tex 2000/06/30 17:58:34 1.78
***************
*** 1399,1403 ****
arguments is that functions often pass the objects they receive on to
other function --- if each function were to test for \NULL{},
! there would be a lot of redundant tests and the code would run slower.
It is better to test for \NULL{} only at the ``source'', i.e.\ when a
--- 1399,1404 ----
arguments is that functions often pass the objects they receive on to
other function --- if each function were to test for \NULL{},
! there would be a lot of redundant tests and the code would run more
! slowly.
It is better to test for \NULL{} only at the ``source'', i.e.\ when a
***************
*** 1423,1427 ****
It is a severe error to ever let a \NULL{} pointer ``escape'' to
! the Python user.
--- 1424,1434 ----
It is a severe error to ever let a \NULL{} pointer ``escape'' to
! the Python user.
!
! % Frank Stajano:
! % A pedagogically buggy example, along the lines of the previous listing,
! % would be helpful here -- showing in more concrete terms what sort of
! % actions could cause the problem. I can't very well imagine it from the
! % description.