From: johan rydberg <johan@rydberg.com>
To: cgen@sources.redhat.com
Subject: [patch] doc/pmacros.texi
Date: Sat, 13 Oct 2001 02:47:00 -0000 [thread overview]
Message-ID: <20011116041936.C11896@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
Well. I do not know if comments for pmacros is deprecated, but if not,
here's a small patch that documents the argument.
2001-11-16 Johan Rydberg <johan@rydberg.com>
* doc/pmacros.texi (Defining a preprocessor macro): Document
"comment" argument for (define-pmacro ...).
--
Johan Rydberg
$ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") -
THEN EXCUSE/OBJECT=ME
[-- Attachment #2: pmacros.texti-patch --]
[-- Type: application/octet-stream, Size: 912 bytes --]
Index: pmacros.texi
===================================================================
RCS file: /cvs/src/src/cgen/doc/pmacros.texi,v
retrieving revision 1.2
diff -u -u -r1.2 pmacros.texi
--- pmacros.texi 2001/03/19 03:36:24 1.2
+++ pmacros.texi 2001/11/16 02:58:22
@@ -37,7 +37,7 @@
Preprocessor macros are defined with:
@smallexample
-(define-pmacro (name parm1 parm2 ... parmN)
+(define-pmacro (name parm1 parm2 ... parmN) [comment]
expansion
)
@end smallexample
@@ -45,7 +45,7 @@
The result is @samp{expansion} with parameters replaced with the actual
arguments of the macro invocation. Free variables are left unchanged.
[A "free variable", as defined here, is one that doesn't appear in the
-parameter list.]
+parameter list.] @samp{comment} is an optional string.
@c ??? This used to be true, but currently isn't.
@c If the result is another macro invocation, it is expanded in turn.
WARNING: multiple messages have this Message-ID
From: johan rydberg <johan@rydberg.com>
To: cgen@sources.redhat.com
Subject: [patch] doc/pmacros.texi
Date: Thu, 15 Nov 2001 19:16:00 -0000 [thread overview]
Message-ID: <20011116041936.C11896@localhost> (raw)
Message-ID: <20011115191600.K1Gv2aK6J9s_Jx54JYfLFYtlKkWIFVo5e_bnDJT5SMQ@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
Well. I do not know if comments for pmacros is deprecated, but if not,
here's a small patch that documents the argument.
2001-11-16 Johan Rydberg <johan@rydberg.com>
* doc/pmacros.texi (Defining a preprocessor macro): Document
"comment" argument for (define-pmacro ...).
--
Johan Rydberg
$ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") -
THEN EXCUSE/OBJECT=ME
[-- Attachment #2: pmacros.texti-patch --]
[-- Type: text/x-diff, Size: 912 bytes --]
Index: pmacros.texi
===================================================================
RCS file: /cvs/src/src/cgen/doc/pmacros.texi,v
retrieving revision 1.2
diff -u -u -r1.2 pmacros.texi
--- pmacros.texi 2001/03/19 03:36:24 1.2
+++ pmacros.texi 2001/11/16 02:58:22
@@ -37,7 +37,7 @@
Preprocessor macros are defined with:
@smallexample
-(define-pmacro (name parm1 parm2 ... parmN)
+(define-pmacro (name parm1 parm2 ... parmN) [comment]
expansion
)
@end smallexample
@@ -45,7 +45,7 @@
The result is @samp{expansion} with parameters replaced with the actual
arguments of the macro invocation. Free variables are left unchanged.
[A "free variable", as defined here, is one that doesn't appear in the
-parameter list.]
+parameter list.] @samp{comment} is an optional string.
@c ??? This used to be true, but currently isn't.
@c If the result is another macro invocation, it is expanded in turn.
next reply other threads:[~2001-11-16 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 2:47 johan rydberg [this message]
2001-11-15 19:16 ` johan rydberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011116041936.C11896@localhost \
--to=johan@rydberg.com \
--cc=cgen@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).