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

update documentation on what constitutes a line in a source file 

(closes SF bug #1167922)
This commit is contained in:
Fred Drake 2005-05-25 05:29:17 +00:00
parent bbf12ba7b2
commit db22958f07
1 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Doc/ref/ref2.tex
View File

@ -54,11 +54,18 @@ by following the explicit or implicit \emph{line joining} rules.
\subsection{Physical lines\label{physical}}
A physical line ends in whatever the current platform's convention is
for terminating lines. On \UNIX, this is the \ASCII{} LF (linefeed)
character. On Windows, it is the \ASCII{} sequence CR LF (return
followed by linefeed). On Macintosh, it is the \ASCII{} CR (return)
character.
A physical line is a sequence of characters terminated by an end-of-line
sequence. In source files, any of the standard platform line
termination sequences can be used - the \UNIX form using \ASCII{} LF
(linefeed), the Windows form using the \ASCII{} sequence CR LF (return
followed by linefeed), or the Macintosh form using the \ASCII{} CR
(return) character. All of these forms can be used equally, regardless
of platform.
When embedding Python, source code strings should be passed to Python
APIs using the standard C conventions for newline characters (the
\code{\e n} character, representing \ASCII{} LF, is the line
terminator).
\subsection{Comments\label{comments}}