Index: ChangeLog
===================================================================
RCS file: /cvsroot/emacs/emacs/lispref/ChangeLog,v
retrieving revision 1.488
diff -r1.488 ChangeLog
0a1,5
> 2005-09-07 Joshua Varner  <jlvarner@gmail.com>
> 
> 	* objects.texi (Comments): Remove node.
> 	* intro.texi (Comments): Add node.
> 	
Index: intro.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/lispref/intro.texi,v
retrieving revision 1.31
diff -r1.31 intro.texi
147a148
> * Comments::                    Comments and their formatting conventions.
213a215,234
> 
> @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.
> 
>   The @samp{#@@@var{count}} construct, which skips the next @var{count}
> characters, is useful for program-generated comments containing binary
> data.  The Emacs Lisp byte compiler uses this in its output files
> (@pxref{Byte Compilation}).  It isn't meant for source files, however.
> 
>   @xref{Comment Tips}, for conventions for formatting comments.
Index: objects.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/lispref/objects.texi,v
retrieving revision 1.48
diff -r1.48 objects.texi
55d54
< * Comments::                    Comments and their formatting conventions.
109,129d107
< 
< @node Comments
< @comment  node-name,  next,  previous,  up
< @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.
< 
<   The @samp{#@@@var{count}} construct, which skips the next @var{count}
< characters, is useful for program-generated comments containing binary
< data.  The Emacs Lisp byte compiler uses this in its output files
< (@pxref{Byte Compilation}).  It isn't meant for source files, however.
< 
<   @xref{Comment Tips}, for conventions for formatting comments.