Update of /cvsroot/python/python/dist/src/Doc/ref
In directory usw-pr-cvs1:/tmp/cvs-serv5033/ref
Modified Files:
ref3.tex
Log Message:
Fix up Guido's markup.
Index: ref3.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/ref/ref3.tex,v
retrieving revision 1.89
retrieving revision 1.90
diff -C2 -d -r1.89 -r1.90
*** ref3.tex 3 Jun 2002 19:06:41 -0000 1.89
--- ref3.tex 4 Jun 2002 16:25:57 -0000 1.90
***************
*** 13,17 ****
Every object has an identity, a type and a value. An object's
\emph{identity} never changes once it has been created; you may think
! of it as the object's address in memory. The `\code{is}' operator
compares the identity of two objects; the
\function{id()}\bifuncindex{id} function returns an integer
--- 13,17 ----
Every object has an identity, a type and a value. An object's
\emph{identity} never changes once it has been created; you may think
! of it as the object's address in memory. The `\keyword{is}' operator
compares the identity of two objects; the
\function{id()}\bifuncindex{id} function returns an integer
***************
*** 1541,1548 ****
\item
! New-style classes (those derived from \code{object}) never invoke the
! \code{__coerce__} method in response to a binary operator; the only
! time \code{__coerce__} is invoked is when the built-in function
! \code{coerce()} is called.
\item
--- 1541,1548 ----
\item
! New-style classes (those derived from \class{object}) never invoke the
! \method{__coerce__()} method in response to a binary operator; the only
! time \method{__coerce__()} is invoked is when the built-in function
! \function{coerce()} is called.
\item
***************
*** 1566,1570 ****
is tried. If this is not implemented or returns \code{NotImplemented},
\code{\var{y}.__rop__(\var{x})} is tried. If this is also not
! implemented or returns \code{NotImplemented}, a \code{TypeError}
exception is raised. But see the following exception:
--- 1566,1570 ----
is tried. If this is not implemented or returns \code{NotImplemented},
\code{\var{y}.__rop__(\var{x})} is tried. If this is also not
! implemented or returns \code{NotImplemented}, a \exception{TypeError}
exception is raised. But see the following exception:
***************
*** 1574,1579 ****
a built-in type or a new-style class, and the right operand is an
instance of a proper subclass of that type or class, the right
! operand's \code{__rop__} method is tried \emph{before} the left
! operand's \code{__op__} method. This is done so that a subclass can
completely override binary operators. Otherwise, the left operand's
__op__ method would always accept the right operand: when an instance
--- 1574,1579 ----
a built-in type or a new-style class, and the right operand is an
instance of a proper subclass of that type or class, the right
! operand's \method{__rop__()} method is tried \emph{before} the left
! operand's \method{__op__()} method. This is done so that a subclass can
completely override binary operators. Otherwise, the left operand's
__op__ method would always accept the right operand: when an instance
***************
*** 1584,1598 ****
When either operand type defines a coercion, this coercion is called
! before that type's \code{__op__} or \code{__rop__} method is called,
! but no sooner. If the coercion returns an object of a different type
! for the operand whose coercion is invoked, part of the process is
! redone using the new object.
\item
When an in-place operator (like `\code{+=}') is used, if the left
! operand implements \code{__iop__}, it is invoked without any coercion.
! When the operation falls back to \code{__op__} and/or \code{__rop__},
! the normal coercion rules apply.
\item
--- 1584,1598 ----
When either operand type defines a coercion, this coercion is called
! before that type's \method{__op__()} or \method{__rop__()} method is
! called, but no sooner. If the coercion returns an object of a
! different type for the operand whose coercion is invoked, part of the
! process is redone using the new object.
\item
When an in-place operator (like `\code{+=}') is used, if the left
! operand implements \method{__iop__()}, it is invoked without any
! coercion. When the operation falls back to \method{__op__()} and/or
! \method{__rop__()}, the normal coercion rules apply.
\item
***************
*** 1605,1626 ****
In \var{x}\code{*}\var{y}, if one operator is a sequence that
implements sequence repetition, and the other is an integer
! (\code{int} or \code{long}), sequence repetition is invoked.
\item
! Rich comparisons (implemented by methods \code{__eq__} and so on)
never use coercion. Three-way comparison (implemented by
! \code{__cmp__}) does use coercion under the same conditions as
other binary operations use it.
\item
! In the current implementation, the built-in numeric types \code{int},
! \code{long} and \code{float} do not use coercion; the type
! \code{complex} however does use it. The difference can become
apparent when subclassing these types. Over time, the type
! \code{complex} may be fixed to avoid coercion. All these types
! implement a \code{__coerce__} method, for use by the built-in
! \code{coerce} function.
\end{itemize}
--- 1605,1626 ----
In \var{x}\code{*}\var{y}, if one operator is a sequence that
implements sequence repetition, and the other is an integer
! (\class{int} or \class{long}), sequence repetition is invoked.
\item
! Rich comparisons (implemented by methods \method{__eq__()} and so on)
never use coercion. Three-way comparison (implemented by
! \method{__cmp__()}) does use coercion under the same conditions as
other binary operations use it.
\item
! In the current implementation, the built-in numeric types \class{int},
! \class{long} and \class{float} do not use coercion; the type
! \class{complex} however does use it. The difference can become
apparent when subclassing these types. Over time, the type
! \class{complex} may be fixed to avoid coercion. All these types
! implement a \method{__coerce__()} method, for use by the built-in
! \function{coerce()} function.
\end{itemize}
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4