summaryrefslogtreecommitdiff
path: root/Doc
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1994-02-24 11:28:27 +0000
committerGuido van Rossum <guido@python.org>1994-02-24 11:28:27 +0000
commit68cfbe7c93f8525da14ef419940df3c4b81f1ff4 (patch)
tree7a9ae6b7bd42f95b1be5864baff26254570ddb43 /Doc
parent9f65ae0093e45eeadc5ed8c5cb3a9fc1f9b29f95 (diff)
downloadcpython-git-68cfbe7c93f8525da14ef419940df3c4b81f1ff4.tar.gz
Documented xrange; crossreffed lambda a bit more
Diffstat (limited to 'Doc')
-rw-r--r--Doc/lib/libfuncs.tex12
-rw-r--r--Doc/libfuncs.tex12
2 files changed, 24 insertions, 0 deletions
diff --git a/Doc/lib/libfuncs.tex b/Doc/lib/libfuncs.tex
index e0b36f33d7..73bc1454b7 100644
--- a/Doc/lib/libfuncs.tex
+++ b/Doc/lib/libfuncs.tex
@@ -354,3 +354,15 @@ its goal is to return a printable string.
>>> if type(x) == type(''): print 'It is a string'
\end{verbatim}\ecode
\end{funcdesc}
+
+\begin{funcdesc}{xrange}{start\, end\, step}
+This function is very similar to \code{range()}, but returns an
+``xrange object'' instead of a list. This is an opaque sequence type
+which yields the same values as the corresponding list, without
+actually storing them all simultaneously. The advantage of
+\code{xrange()} over \code{range()} is minimal (since \code{xrange()}
+still has to create the values when asked for them) except when a very
+large range is used on a memory-starved machine (e.g. DOS) or when all
+of the range's elements are never used (e.g. when the loop is usually
+terminated with \code{break}).
+\end{funcdesc}
diff --git a/Doc/libfuncs.tex b/Doc/libfuncs.tex
index e0b36f33d7..73bc1454b7 100644
--- a/Doc/libfuncs.tex
+++ b/Doc/libfuncs.tex
@@ -354,3 +354,15 @@ its goal is to return a printable string.
>>> if type(x) == type(''): print 'It is a string'
\end{verbatim}\ecode
\end{funcdesc}
+
+\begin{funcdesc}{xrange}{start\, end\, step}
+This function is very similar to \code{range()}, but returns an
+``xrange object'' instead of a list. This is an opaque sequence type
+which yields the same values as the corresponding list, without
+actually storing them all simultaneously. The advantage of
+\code{xrange()} over \code{range()} is minimal (since \code{xrange()}
+still has to create the values when asked for them) except when a very
+large range is used on a memory-starved machine (e.g. DOS) or when all
+of the range's elements are never used (e.g. when the loop is usually
+terminated with \code{break}).
+\end{funcdesc}