parent
be9b765c07
commit
a12a86e956
|
@ -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
|
||||
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
|
||||
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
|
||||
|
|
|
@ -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
|
||||
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`
|
||||
structure for different C libraries can be different and incompatible. Under
|
||||
Windows (at least), it is possible for dynamically linked extensions to actually
|
||||
|
|
Loading…
Reference in New Issue