traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Document handling of raw-unicode-escapes. Closes SF bug 587087.

This commit is contained in:
Raymond Hettinger 2002-08-06 22:36:26 +00:00
parent 5814187f5b
commit d9fdb51df6
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Doc/ref/ref2.tex
View File

@ -457,6 +457,14 @@ escape the following quote character). Note also that a single
backslash followed by a newline is interpreted as those two characters backslash followed by a newline is interpreted as those two characters
as part of the string, \emph{not} as a line continuation. as part of the string, \emph{not} as a line continuation.
When an `r' or `R' prefix is used in conjunction with a `u' or `U'
prefix, then the \uXXXX escape sequence is processed while \emph{all other
backslashes are left in the string}. For example, the string literal
\code{ur"\u0062\n"} consists of three Unicode characters:
`LATIN SMALL LETTER B', `REVERSE SOLIDUS', and `LATIN SMALL LETTER N'.
Backslashes can be escaped with a preceding backslash; however, both
remain in the string. As a result, \uXXXX escape sequences are
only recognized when there are an odd number of backslashes.
\subsection{String literal concatenation\label{string-catenation}} \subsection{String literal concatenation\label{string-catenation}}