From b9032018ffaf6b4fb1eeeee44f9ee9ac0b407114 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Thu, 2 May 2002 21:37:23 +0000 Subject: [PATCH] Update the xrange object description to reflect the removal of deprecated features. --- Doc/lib/libstdtypes.tex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Doc/lib/libstdtypes.tex b/Doc/lib/libstdtypes.tex index 0cd62894810..65e315239b6 100644 --- a/Doc/lib/libstdtypes.tex +++ b/Doc/lib/libstdtypes.tex @@ -401,9 +401,9 @@ new buffer object. 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 or concatenation, but do support repetition, and using -\code{in}, \code{not in}, \function{min()} or \function{max()} on them -is inefficient. +slicing, concatenation, or repetition, and using \keyword{in}, +\keyword{not} \keyword{in}, \function{min()} or \function{max()} on +them is inefficient. \obindex{xrange} Most sequence types support the following operations. The \samp{in} and