From 40e1db8ccd1239fc7da5ccd3f5f79017b2b44afc Mon Sep 17 00:00:00 2001 From: Noam Postavsky Date: Wed, 20 Jun 2018 08:40:51 -0400 Subject: Change index of ";" to better reflect it's usage (Bug#31623) * doc/lispref/objects.texi (Comments): "; for commenting" fits better with the following text about how a semicolon begins a comment. Also mention that only unescaped semicolons start a comment. --- doc/lispref/objects.texi | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/doc/lispref/objects.texi b/doc/lispref/objects.texi index c7e751cbd8c..b8cae49027c 100644 --- a/doc/lispref/objects.texi +++ b/doc/lispref/objects.texi @@ -109,15 +109,15 @@ not be evaluated later. @xref{Input Functions}, for a description of @node Comments @section Comments @cindex comments -@cindex @samp{;} in comment - - A @dfn{comment} is text that is written in a program only for the sake -of humans that read the program, and that has no effect on the meaning -of the program. In Lisp, a semicolon (@samp{;}) starts a comment if it -is not within a string or character constant. The comment continues to -the end of line. The Lisp reader discards comments; they do not become -part of the Lisp objects which represent the program within the Lisp -system. +@cindex @samp{;} for commenting + + A @dfn{comment} is text that is written in a program only for the +sake of humans that read the program, and that has no effect on the +meaning of the program. In Lisp, an unescaped semicolon (@samp{;}) +starts a comment if it is not within a string or character constant. +The comment continues to the end of line. The Lisp reader discards +comments; they do not become part of the Lisp objects which represent +the program within the Lisp system. The @samp{#@@@var{count}} construct, which skips the next @var{count} characters, is useful for program-generated comments containing binary -- cgit v1.2.1