Mercurial > cpython-lru_cache-weakref
diff Doc/lib/libstdtypes.tex @ 23341:55423c1abcd1 2.2
Correct information on support for repietition & concatenation for buffer
and xrange objects.
This closes SF bug #550555.
| author | Fred Drake <fdrake@acm.org> |
|---|---|
| date | Thu, 02 May 2002 05:57:07 +0000 |
| parents | a443e5e5ece7 |
| children | 67bcb4f5237f |
line wrap: on
line diff
--- a/Doc/lib/libstdtypes.tex Thu May 02 04:51:37 2002 +0000 +++ b/Doc/lib/libstdtypes.tex Thu May 02 05:57:07 2002 +0000 @@ -388,15 +388,17 @@ Buffer objects are not directly supported by Python syntax, but can be created by calling the builtin function -\function{buffer()}.\bifuncindex{buffer}. They don't support -concatenation or repetition. +\function{buffer()}.\bifuncindex{buffer}. They support +concatenation and repetition, but the result is a new string object +rather than a new buffer object. \obindex{buffer} Xrange objects are similar to buffers in that there is no specific -syntax to create them, but they are created using the \function{xrange()} -function.\bifuncindex{xrange} They don't support slicing, -concatenation or repetition, and using \code{in}, \code{not in}, -\function{min()} or \function{max()} on them is inefficient. +syntax to create them, but they are created using the +\function{xrange()} function.\bifuncindex{xrange} They don't support +slicing or concatenation, but do support repetition, and using +\code{in}, \code{not in}, \function{min()} or \function{max()} on them +is inefficient. \obindex{xrange} Most sequence types support the following operations. The \samp{in} and
