[Python-checkins] python/dist/src/Doc/api intro.tex, 1.6,
1.6.4.1 memory.tex, 1.2, 1.2.22.1
rhettinger at users.sourceforge.net
rhettinger at users.sourceforge.net
Sat Jan 1 01:35:24 CET 2005
- Previous message: [Python-checkins]
python/dist/src/Doc/whatsnew whatsnew20.tex, 1.52,
1.52.2.1 whatsnew21.tex, 1.33, 1.33.4.1 whatsnew23.tex, 1.166,
1.166.2.1 whatsnew24.tex, 1.118, 1.118.2.1
- Next message: [Python-checkins] python/dist/src/Doc/dist dist.tex,1.86,1.86.2.1
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Update of /cvsroot/python/python/dist/src/Doc/api
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv5382/api
Modified Files:
Tag: release24-maint
intro.tex memory.tex
Log Message:
SF Patch #1093896: miscellaneous doc typos
Index: intro.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/api/intro.tex,v
retrieving revision 1.6
retrieving revision 1.6.4.1
diff -u -d -r1.6 -r1.6.4.1
--- intro.tex 31 Mar 2004 07:45:46 -0000 1.6
+++ intro.tex 1 Jan 2005 00:34:52 -0000 1.6.4.1
@@ -277,7 +277,7 @@
The situation is slightly different for function return values.
While passing a reference to most functions does not change your
ownership responsibilities for that reference, many functions that
-return a referece to an object give you ownership of the reference.
+return a reference to an object give you ownership of the reference.
The reason is simple: in many cases, the returned object is created
on the fly, and the reference you get is the only reference to the
object. Therefore, the generic functions that return object
Index: memory.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/api/memory.tex,v
retrieving revision 1.2
retrieving revision 1.2.22.1
diff -u -d -r1.2 -r1.2.22.1
--- memory.tex 6 Apr 2002 09:14:33 -0000 1.2
+++ memory.tex 1 Jan 2005 00:34:52 -0000 1.2.22.1
@@ -134,7 +134,7 @@
In addition, the following macro sets are provided for calling the
Python memory allocator directly, without involving the C API functions
listed above. However, note that their use does not preserve binary
-compatibility accross Python versions and is therefore deprecated in
+compatibility across Python versions and is therefore deprecated in
extension modules.
\cfunction{PyMem_MALLOC()}, \cfunction{PyMem_REALLOC()}, \cfunction{PyMem_FREE()}.
- Previous message: [Python-checkins]
python/dist/src/Doc/whatsnew whatsnew20.tex, 1.52,
1.52.2.1 whatsnew21.tex, 1.33, 1.33.4.1 whatsnew23.tex, 1.166,
1.166.2.1 whatsnew24.tex, 1.118, 1.118.2.1
- Next message: [Python-checkins] python/dist/src/Doc/dist dist.tex,1.86,1.86.2.1
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Python-checkins
mailing list