Eric Blake <ebb9 <at> byu.net> writes:
>
> And finally, the patch I've been working on for a week, which turned up
> all the smaller issues along the way. I changed the formatting to use
> <at> deffn consistently, fixed grammar mistakes as I saw them, and adjusted
> wording where it was awkward. I've tested info, pdf, and html outputs to
> make sure all three look reasonable.
The node on builtin had some bad merging.
2006-07-17 Eric Blake <[EMAIL PROTECTED]>
* doc/m4.texinfo (Builtin): Delete redundant text.
Index: doc/m4.texinfo
===================================================================
RCS file: /sources/m4/m4/doc/m4.texinfo,v
retrieving revision 1.1.1.1.2.46
diff -u -r1.1.1.1.2.46 m4.texinfo
--- doc/m4.texinfo 15 Jul 2006 22:08:58 -0000 1.1.1.1.2.46
+++ doc/m4.texinfo 17 Jul 2006 16:51:10 -0000
@@ -1636,7 +1636,7 @@
@end deffn
This can be used even if @var{name} has been given another definition
-that has covered the original, or been undefined so that no @var{name}
+that has covered the original, or been undefined so that no macro
maps to the builtin.
@example
@@ -1662,54 +1662,9 @@
@result{}foo
@end example
-Note that this can be used to invoke builtins that normally require
-parameters without actually providing them; but it will provoke a
-warning, and usually result in a void expansion.
-
[EMAIL PROTECTED]
-builtin
[EMAIL PROTECTED]
-builtin()
[EMAIL PROTECTED]:2: m4: undefined builtin `'
[EMAIL PROTECTED]
-builtin(`builtin')
[EMAIL PROTECTED]:3: m4: Warning: too few arguments to builtin `builtin'
[EMAIL PROTECTED]
-builtin(`builtin',)
[EMAIL PROTECTED]:4: m4: undefined builtin `'
[EMAIL PROTECTED]
[EMAIL PROTECTED] example
-
-This can be used even if @var{name} has been given another definition
-that has covered the original, or been undefined so that no @var{name}
-maps to the builtin.
-
[EMAIL PROTECTED]
-pushdef(`define', `hidden')
[EMAIL PROTECTED]
-undefine(`undefine')
[EMAIL PROTECTED]
-define(`foo', `bar')
[EMAIL PROTECTED]
-foo
[EMAIL PROTECTED]
-builtin(`define', `foo', `BAR')
[EMAIL PROTECTED]
-foo
[EMAIL PROTECTED]
-undefine(`foo')
[EMAIL PROTECTED](foo)
-foo
[EMAIL PROTECTED]
-builtin(`undefine', `foo')
[EMAIL PROTECTED]
-foo
[EMAIL PROTECTED]
[EMAIL PROTECTED] example
-
-Note that this can be used to invoke builtins that normally require
-parameters without actually providing them; but it will provoke a
-warning, and usually result in a void expansion.
+Note that this can be used to invoke builtins without arguments, even
+when they normally require parameters to be recognized; but it will
+provoke a warning, and result in a void expansion.
@example
builtin
_______________________________________________
M4-patches mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/m4-patches
