From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: Deprecation question - is proposed code-change back-portable to V1.8.7?
Date: Sun, 19 Aug 2012 11:50:13 +0200 [thread overview]
Message-ID: <87ehn3i52i.fsf@pobox.com> (raw)
In-Reply-To: <874no3hrnc.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 16 Aug 2012 15:51:03 +0200")
On Thu 16 Aug 2012 15:51, ludo@gnu.org (Ludovic Courtès) writes:
>> and if so, does Guile 1.8.7 do exactly the same as Guile 2.06?
>
> Yes, but unfortunately, ‘scm_module_variable’ didn’t exist in Guile
> 1.8. So you’ll have to #ifdef to use one or the other.
Better to just define scm_module_variable in guile 1.8:
#if defined (SCM_MAJOR_VERSION) && (SCM_MAJOR_VERSION < 2)
SCM
scm_module_variable (SCM module, SCM sym)
{
return scm_sym2var (sym, scm_module_lookup_closure (module), SCM_BOOL_F);
}
#endif
Cheers,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2012-08-19 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 11:30 Deprecation question - is proposed code-change back-portable to V1.8.7? Ian Hulin
2012-08-16 13:51 ` Ludovic Courtès
2012-08-16 23:04 ` Ian Hulin
2012-08-19 9:50 ` Andy Wingo [this message]
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=87ehn3i52i.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).