From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: snarfer guard macro name decision: SCM_MAGIC_SNARFER
Date: Thu, 14 Mar 2002 20:26:23 -0800 [thread overview]
Message-ID: <E16ljIN-0007ql-00@giblet> (raw)
In-Reply-To: <87r8mmwwn8.fsf@zagadka.ping.de> (message from Marius Vollmer on 15 Mar 2002 00:35:23 +0100)
From: Marius Vollmer <mvo@zagadka.ping.de>
Date: 15 Mar 2002 00:35:23 +0100
> why isn't SCM_VCELL in HEAD branch snarf.h?
It is deprecated in the 1.6 branch and all things that are deprecated
in 1.6 are already removed from HEAD. It is deprecated in the 1.6
branch because the whole concept of vcells has been deprecated. This
has been done to clean up a confusing between glocs and structs and to
make the memoized code be a proper Scheme data structure. Also, some
bindings where done with variables, and some not. Now all bindings
are done with variables which makes for a better integration of the
module system into the rest of Guile.
> how do you propose to handle the situation where a user has
> SCM_VCELL but would like to use guile-1.8?
He should remove all uses of vcells and switch to variables.
thanks for the explanation (which is also touched upon in NEWS -- i
should have looked there first). looks like "1.4 compatibility" in
snarfing has no value in the long run, so "guile-snarf --compat=1.4"
support is misguided and can be removed. i'll replace it with detection
of the deprecated macros, which for 1.6 would result in a warning, and
1.8 would result in an error.
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-15 4:26 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
2002-03-14 20:44 ` Thien-Thi Nguyen
2002-03-14 23:35 ` Marius Vollmer
2002-03-15 4:26 ` Thien-Thi Nguyen [this message]
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=E16ljIN-0007ql-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-devel@gnu.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).