m4-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Changes to m4/doc/m4.texinfo,v [branch-1_4]


From: Eric Blake
Subject: Changes to m4/doc/m4.texinfo,v [branch-1_4]
Date: Tue, 01 Aug 2006 13:05:47 +0000

CVSROOT:        /sources/m4
Module name:    m4
Branch:         branch-1_4
Changes by:     Eric Blake <ericb>      06/08/01 13:05:45

Index: doc/m4.texinfo
===================================================================
RCS file: /sources/m4/m4/doc/m4.texinfo,v
retrieving revision 1.1.1.1.2.58
retrieving revision 1.1.1.1.2.59
diff -u -b -r1.1.1.1.2.58 -r1.1.1.1.2.59
--- doc/m4.texinfo      1 Aug 2006 02:53:35 -0000       1.1.1.1.2.58
+++ doc/m4.texinfo      1 Aug 2006 13:05:45 -0000       1.1.1.1.2.59
@@ -1043,10 +1043,9 @@
 @example
 define(
 ^D
address@hidden:0: m4: ERROR: end of file in argument list
address@hidden:stdin:1: ERROR: end of file in argument list
 @end example
 
-
 @node Quoting Arguments
 @section Quoting macro arguments
 
@@ -2317,7 +2316,7 @@
 ')0 hi dnl 1 hi')
 @result{}
 ^D
address@hidden:0: m4: Warning: end of file treated as newline
address@hidden:NONE:0: Warning: end of file treated as newline
 @result{}0 HI 2 HI
 @end example
 
@@ -2454,7 +2453,7 @@
 @example
 `dangling quote
 ^D
address@hidden:0: m4: ERROR: end of file in string
address@hidden:stdin:1: ERROR: end of file in string
 @end example
 
 @node Changecom
@@ -2551,7 +2550,7 @@
 @result{}
 /*dangling comment
 ^D
address@hidden:0: m4: ERROR: end of file in comment
address@hidden:stdin:1: ERROR: end of file in comment
 @end example
 
 @node Changeword
@@ -2778,7 +2777,7 @@
 m4wrap(`m4wrap(`)')len(abc')
 @result{}
 ^D
address@hidden:0: m4: ERROR: end of file in argument list
address@hidden:NONE:0: ERROR: end of file in argument list
 @end example
 
 @node File Inclusion
@@ -4054,6 +4053,11 @@
 @result{}
 @end example
 
+Currently, all text wrapped with @code{m4wrap} (@pxref{M4wrap}) behaves
+as though it came from line 0 of the file ``NONE''.  It is hoped that a
+future release of @code{m4} can overcome this limitation and remember
+which file invoked the call to @code{m4wrap}.
+
 @node M4exit
 @section Exiting from @code{m4}
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]