From: Ian Hulin <ian@hulin.org.uk>
To: guile-user@gnu.org
Subject: Deprecation question - is proposed code-change back-portable to V1.8.7?
Date: Thu, 16 Aug 2012 12:30:26 +0100 [thread overview]
Message-ID: <k0ilkh$vv5$1@ger.gmane.org> (raw)
Hi all,
In working with Guile V2.0.6, compiling the following code gives
deprecation errors for both scm_sym2var and scm_module_lookup_closure.
From looking at the docs following the recommendations in the
deprecation messages, it looks like the offending line needs to change to
return scm_module_variable ( module, sym);
Does scm_module_variable internally do what scm_module_lookup_closure
did, and if so, does Guile 1.8.7 do exactly the same as Guile 2.06?
Asking hear as we're getting near to a release and I don't want to
break anything bigtime on the LilyPond repo.
Cheers,
Ian Hulin
/* Lookup SYM, but don't give error when it is not defined. */
SCM
ly_module_lookup (SCM module, SCM sym)
{
#define FUNC_NAME __FUNCTION__
SCM_VALIDATE_MODULE (1, module);
return scm_sym2var (sym, scm_module_lookup_closure (module),
SCM_BOOL_F);
#undef FUNC_NAME
}
next reply other threads:[~2012-08-16 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 11:30 Ian Hulin [this message]
2012-08-16 13:51 ` Deprecation question - is proposed code-change back-portable to V1.8.7? Ludovic Courtès
2012-08-16 23:04 ` Ian Hulin
2012-08-19 9:50 ` Andy Wingo
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='k0ilkh$vv5$1@ger.gmane.org' \
--to=ian@hulin.org.uk \
--cc=guile-user@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).