From: Andy Wingo <wingo@pobox.com>
To: Mark Harig <idirectscm@aim.com>
Cc: bug-guile@gnu.org, lispor@163.com
Subject: Re: Can not work with libguile-2.0
Date: Fri, 18 Feb 2011 09:41:40 +0100 [thread overview]
Message-ID: <m3wrkx20qj.fsf@unquote.localdomain> (raw)
In-Reply-To: <8CD9CE6E0B29934-235C-1DA91@Webmail-m118.sysops.aol.com> (Mark Harig's message of "Thu, 17 Feb 2011 13:23:24 -0500")
Hello,
On Thu 17 Feb 2011 19:23, Mark Harig <idirectscm@aim.com> writes:
>> And in section 2.4(Writing Guile Extensions)
>> There are some deprecated functions in the example
>
> Agreed. The example code uses deprecated functions. It would better
> if the developers of Guile were to provide some idiomatic code that
> shows the best practice that they recommend programmers use.
Agreed, thanks for catching this; fixed. Patches fixing problems like
this are most welcome in the future. NEWS should contain details about
deprecated functions and their replacements.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-02-18 8:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 12:02 Can not work with libguile-2.0 Fu-Gangqiang
2011-02-17 13:02 ` Hans Aberg
2011-02-17 13:40 ` Fu-Gangqiang
2011-02-17 18:04 ` Mark Harig
2011-02-17 18:23 ` Mark Harig
2011-02-18 8:41 ` Andy Wingo [this message]
2011-02-17 19:08 ` Mark Harig
2011-02-18 8:53 ` Andy Wingo
2011-02-18 19:42 ` Mark Harig
2011-02-20 10:13 ` Andy Wingo
2011-02-18 1:39 ` Fu-Gangqiang
2011-02-18 8:34 ` Andy Wingo
2011-02-19 15:30 ` linking with libguile-2.0, rpath Bruno Haible
2011-02-20 10:58 ` 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=m3wrkx20qj.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=idirectscm@aim.com \
--cc=lispor@163.com \
/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).