From: Ian Hulin <ian@hulin.org.uk>
To: guile-user@gnu.org
Subject: Re: Deprecation question - is proposed code-change back-portable to V1.8.7?
Date: Fri, 17 Aug 2012 00:04:28 +0100 [thread overview]
Message-ID: <k0ju9r$o44$1@ger.gmane.org> (raw)
In-Reply-To: <874no3hrnc.fsf@gnu.org>
Hi Ludo,
Many thanks for the quick response,
Cheers,
Ian
On 16/08/12 14:51, Ludovic � wrote:
> Hi,
>
> Ian Hulin <ian@hulin.org.uk> skribis:
>
>> 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,
>
> Yes.
>
>> 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.
>
> Thanks, Ludo’.
>
>
>
next prev parent reply other threads:[~2012-08-16 23:04 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 [this message]
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='k0ju9r$o44$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).