From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: snarfer guard macro name decision: SCM_MAGIC_SNARFER
Date: 14 Mar 2002 19:48:55 +0100 [thread overview]
Message-ID: <87zo1bx9wo.fsf@zagadka.ping.de> (raw)
In-Reply-To: <E16lIra-0006Dx-00@giblet>
Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
> old_school_snarf ()
> {
> sed -e 's/SCM_CONST_LONG/SCM_GLOBAL_VCELL_INIT/g' \
> -e 's/SCM_GLOBAL_VCELL_INIT/SCM_GLOBAL_VARIABLE_INIT/g' \
> -e 's/SCM_GLOBAL_VCELL/SCM_GLOBAL_VARIABLE/g' \
> -e 's/SCM_VCELL_INIT/SCM_VARIABLE_INIT/g' \
> -e 's/SCM_VCELL/SCM_VARIABLE/g' \
> $1 > ${temp}
> cp ${temp} $1
> modern_snarf "$@"
> }
Don't do this. First, SCM_VCELL and SCM_VARIABLE are not the same
thing. You can't substitute one for the other. (Likewise for the
substitutions.) Second, we already keep proper backward compatibility
in the C code itself:
#if (SCM_DEBUG_DEPRECATED == 0)
#define SCM_CONST_LONG(c_name, scheme_name,value) \
SCM_VCELL_INIT(c_name, scheme_name, scm_long2num(value))
etc...
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-14 18:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 7:51 snarfer guard macro name decision: SCM_MAGIC_SNARFER Thien-Thi Nguyen
2002-03-13 9:26 ` 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 [this message]
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=87zo1bx9wo.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.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).