From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org
Subject: Re: scm_ documentation
Date: Sun, 26 Feb 2006 07:46:11 +1100 [thread overview]
Message-ID: <87slq7upyk.fsf@zip.com.au> (raw)
In-Reply-To: 43FBA122.1020002@fastmail.fm
Jon Wilson <j85wilson@fastmail.fm> writes:
>
> Everything in this email still applies to 1.6, however.
Alas the 1.6 manual hasn't been getting updates, not beyond the level
of fixing outright errors.
> I actually intended to mean that the gh_ to scm_ section was not a
> very complete documentation of the scm_ interface. Of course, there
> is no reason it should be a complete doc of scm_; that is not its
> purpose.
Yep.
> In the absence of any other scm_ doc, the statement should
> be taken to mean that the only existing doc (that I could find) for
> scm_ is rather incomplete.
In 1.8 it's improving.
> scm_mem2str is the particular one that I was looking for. It is
> mentioned on the gh_ to scm_ transition page as the scm_ replacement
> for gh_str2scm.
Hmm. Yes, alas only digging in the source reveals what it does :-(.
> Also, all of the following are found on the gh_ to scm_ page, but are
> not mentioned in the procedure index.
They've improved in the new release, I think they're all in good shape
now.
> What was I recommending?
I meant if the manual recommends you transition to something, then
that something ought to be described ...
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-02-25 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 0:31 scm_ documentation Jon Wilson
2006-02-21 20:25 ` Kevin Ryde
2006-02-21 23:24 ` Jon Wilson
2006-02-25 20:46 ` Kevin Ryde [this message]
2006-02-25 22:43 ` Jon Wilson
-- strict thread matches above, loose matches on Subject: below --
2006-02-20 22:14 Jon Wilson
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=87slq7upyk.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).