From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Manual reorganized
Date: Fri, 11 Jun 2004 11:34:38 +1000 [thread overview]
Message-ID: <87fz92q3m9.fsf@zip.com.au> (raw)
In-Reply-To: <874qpjjqbn.fsf@zagadka.ping.de> (Marius Vollmer's message of "Thu, 10 Jun 2004 19:06:04 +0200")
Marius Vollmer <mvo@zagadka.de> writes:
>
> What do you
> propose, should we document them.
They're in the 1.6 manual, and I think I added some words to them.
> What is their use?
C "double" funcs corresponding to scheme level round and truncate.
(There's a comment in the code about them being badly named, but it'd
be incompatible to change that now.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-06-11 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 14:51 Manual reorganized Marius Vollmer
2004-05-16 21:56 ` Kevin Ryde
2004-06-10 17:06 ` Marius Vollmer
2004-06-11 1:34 ` Kevin Ryde [this message]
2004-08-09 23:08 ` Marius Vollmer
2004-08-09 23:57 ` Kevin Ryde
2004-08-10 10:36 ` Marius Vollmer
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=87fz92q3m9.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).