From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Undocumented procedures
Date: Tue, 03 Jan 2012 23:05:56 +0100 [thread overview]
Message-ID: <87sjjwjvaz.fsf@gnu.org> (raw)
In-Reply-To: 1325473474.62665.YahooMailNeo@web37901.mail.mud.yahoo.com
Hi!
And happy new year! :-)
Mike Gran <spk121@yahoo.com> skribis:
> scm_display
A matter of adding it as a @deffnx below ‘display’ under “Scheme Write”.
> scm_puts
This and scm_putc should be documented, yes.
> scm_new_port_table_entry
Actually the whole port subsystem is undocumented. :-( So yes, would
be great to document.
> scm_sym2var
It’s public for historical reason, but I personally don’t like it,
because it has a stupid name and complex semantics. ;-)
Depending on what you’re doing, you may be able to use one of the scm_c_
functions in modules.h. WDYT?
Anyway, patches appreciated on the doc front!
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-01-03 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 3:04 Undocumented procedures Mike Gran
2012-01-03 9:15 ` rixed
2012-01-03 22:05 ` Ludovic Courtès [this message]
2012-01-03 22:28 ` Mike Gran
2012-01-07 23:24 ` Andy Wingo
2012-01-07 23:48 ` 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=87sjjwjvaz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).