[6669] ending a macro body with @c documentation

[Gavin D. Smith]

Revision: 6669
          http://svn.sv.gnu.org/viewvc/?view=rev&root=texinfo&revision=6669
Author:   gavin
Date:     2015-10-03 12:01:40 +0000 (Sat, 03 Oct 2015)
Log Message:
-----------
ending a macro body with @c documentation

Modified Paths:
--------------
    trunk/doc/texinfo.texi

Modified: trunk/doc/texinfo.texi
===================================================================
--- trunk/doc/texinfo.texi      2015-10-02 15:31:48 UTC (rev 6668)
+++ trunk/doc/texinfo.texi      2015-10-03 12:01:40 UTC (rev 6669)
@@ -13821,9 +13821,7 @@
 The newline characters after the @code{@@macro} line and before the
 @code{@@end macro} line are ignored, that is, not included in the
 macro body.  All other whitespace is treated according to the usual
-Texinfo rules.  However, there are still undesirable and unpredictable
-interactions between newlines, macros, and commands which are
-line-delimited, as warned about below (@pxref{Macro Details}).
+Texinfo rules.
 
 @cindex Recursive macro invocations
 @findex rmacro
@@ -14116,18 +14114,15 @@
 @c an alternative to @, could be invented if needed.
 
 @item
-It is usually best to avoid comments inside macro definitions, but
-see the next item.
+Ending a macro body with @samp{@@c} may cause text following the macro
+invocation to be ignored as a comment in @command{makeinfo}.  This is 
+not the case when processing with @TeX{} (in case you really want to 
+comment out following text, use @samp{@@comment} instead).  This was
+often done to ``comment out'' an unwanted newline at the end of a macro 
+body, but this is not necessary any more, as the final newline before 
address@hidden@@end macro} is not included in the macro body anyway.
 
 @item
-In general, the interaction of newlines in the macro definitions and
-invocations depends on the precise commands and context,
-notwithstanding the previous statements.  You may be able to work
-around some problems with judicious use of @code{@@c} to ``comment
-out'' a newline, but @code{@@c} will cause problems in other cases.
-We are unable to make any general statements.
-
address@hidden
 In general, you can't arbitrarily substitute a macro (or
 @code{@@value}) call for Texinfo command arguments, even when the text
 is the same.  Texinfo is not M4 (or even plain @TeX{}).  It might work