traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

#5338, #5339: two types in the API manual.

This commit is contained in:
Georg Brandl 2009-02-21 19:09:40 +00:00
parent be9b765c07
commit a12a86e956
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Doc/c-api/intro.rst
View File

@ -187,7 +187,7 @@ caller is said to receive a *new* reference. When no ownership is transferred,
the caller is said to *borrow* the reference. Nothing needs to be done for a the caller is said to *borrow* the reference. Nothing needs to be done for a
borrowed reference. borrowed reference.
Conversely, when a calling function passes it a reference to an object, there Conversely, when a calling function passes in a reference to an object, there
are two possibilities: the function *steals* a reference to the object, or it are two possibilities: the function *steals* a reference to the object, or it
does not. *Stealing a reference* means that when you pass a reference to a does not. *Stealing a reference* means that when you pass a reference to a
function, that function assumes that it now owns that reference, and you are not function, that function assumes that it now owns that reference, and you are not

2
Doc/c-api/veryhigh.rst
View File

@ -16,7 +16,7 @@ parameter. The available start symbols are :const:`Py_eval_input`,
:const:`Py_file_input`, and :const:`Py_single_input`. These are described :const:`Py_file_input`, and :const:`Py_single_input`. These are described
following the functions which accept them as parameters. following the functions which accept them as parameters.
Note also that several of these functions take :ctype:`FILE\*` parameters. On Note also that several of these functions take :ctype:`FILE\*` parameters. One
particular issue which needs to be handled carefully is that the :ctype:`FILE` particular issue which needs to be handled carefully is that the :ctype:`FILE`
structure for different C libraries can be different and incompatible. Under structure for different C libraries can be different and incompatible. Under
Windows (at least), it is possible for dynamically linked extensions to actually Windows (at least), it is possible for dynamically linked extensions to actually