From: Kevin Ryde <user42@zip.com.au>
Subject: Re: When is 1.8 going to be released
Date: Thu, 31 Jul 2003 09:07:47 +1000 [thread overview]
Message-ID: <87he53zk8s.fsf@zip.com.au> (raw)
In-Reply-To: 87n0f6ohar.fsf@zagadka.ping.de
Marius Vollmer <mvo@zagadka.de> writes:
>
> - Implement scm replacements for all of GH
>
> This includes designing the replacement first and writing
> documentation, both tutorial style and reference style.
Speaking of this, it occurred to me while nosing through the
transitioning section that it might be better for the replacements to
be given with each gh function as it's described. For instance
gh_list might say something like
Superseded by `scm_list_n' (*note List Constructors::).
The whole chapter could probably move to be an appendix if it's not
recommended for new programs. Maybe the "Deprecated" chapter could
similarly be an appendix.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-07-30 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 20:24 When is 1.8 going to be released Han-Wen Nienhuys
2003-07-22 12:51 ` Marius Vollmer
2003-07-24 13:09 ` Han-Wen Nienhuys
2003-08-23 17:32 ` Rob Browning
2003-08-27 23:53 ` Kevin Ryde
2003-09-12 16:06 ` Marius Vollmer
2003-07-30 23:07 ` Kevin Ryde [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=87he53zk8s.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).