From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Subject: snarfer guard macro name decision: SCM_MAGIC_SNARFER
Date: Tue, 12 Mar 2002 23:51:38 -0800 [thread overview]
Message-ID: <E16l3Xu-0004hF-00@giblet> (raw)
this was used in 1.4.
libguile-1.6 .c source uses it as #ifndef, however both snarf.h and
guile-snarf have been in the meantime changed to not define this.
1.6 snarfing differs from 1.4 primarily in that there are now two kinds:
init and doc, as opposed to merely init. in defining the names of the
specialization-trigger macros, we now remember usage of this old friend
(i.e., also as guard).
in the end, it is better to migrate self-guard naming internally, and
include that info in the data stream only (snarfing programs generate
program fragments opaque to all re-snarfing).
so, this is sort of a good-bye from public view for SCM_MAGIC_SNARFER
the cpp macro. [band plays.]
anyone know what are the official namespaces allowed for programs that
munge the cpp macro space? [macro looks up, wisened and ready for the
inevitable coup. it is prepared to don a blade, but it has been heard
that the really crafty old dictators (the ones who stayed alive) mingled
and mewed and were the only ones allowed to slit their own throats.]
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-03-13 7:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 7:51 Thien-Thi Nguyen [this message]
2002-03-13 9:26 ` snarfer guard macro name decision: SCM_MAGIC_SNARFER Thien-Thi Nguyen
2002-03-13 19:15 ` Marius Vollmer
2002-03-13 21:28 ` Thien-Thi Nguyen
2002-03-13 22:00 ` Rob Browning
2002-03-13 22:58 ` Thien-Thi Nguyen
2002-03-14 0:12 ` Thien-Thi Nguyen
2002-03-14 5:44 ` Rob Browning
2002-03-14 18:48 ` Marius Vollmer
2002-03-14 20:44 ` Thien-Thi Nguyen
2002-03-14 23:35 ` Marius Vollmer
2002-03-15 4:26 ` Thien-Thi Nguyen
2002-03-15 15:56 ` Thien-Thi Nguyen
2002-03-15 21:19 ` Marius Vollmer
2002-03-14 5:56 ` Thien-Thi Nguyen
2002-03-14 6:58 ` Rob Browning
2002-03-14 7:17 ` Rob Browning
2002-03-14 9:32 ` Thien-Thi Nguyen
2002-03-14 23:40 ` Marius Vollmer
2002-03-14 19:09 ` Marius Vollmer
2002-03-14 22:43 ` Thien-Thi Nguyen
2002-03-14 23:31 ` Rob Browning
2002-03-15 21:12 ` Marius Vollmer
2002-03-15 21:33 ` Rob Browning
2002-03-15 21:58 ` Marius Vollmer
2002-03-17 17:07 ` Rob Browning
2002-03-18 0:07 ` Marius Vollmer
2002-03-18 2:52 ` Rob Browning
2002-03-20 21:11 ` Marius Vollmer
2002-03-21 16:23 ` Rob Browning
2002-04-24 20:07 ` Marius Vollmer
2002-04-24 20:42 ` Rob Browning
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16l3Xu-0004hF-00@giblet \
--to=ttn@giblet.glug.org \
--cc=ttn@glug.org \
/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).