From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Manual reorganized
Date: Tue, 10 Aug 2004 09:57:11 +1000 [thread overview]
Message-ID: <87pt5z27c8.fsf@zip.com.au> (raw)
In-Reply-To: <873c2vx63q.fsf@zagadka.ping.de> (Marius Vollmer's message of "Tue, 10 Aug 2004 01:08:09 +0200")
Marius Vollmer <mvo@zagadka.de> writes:
>
> So what about deprecating them and providing scm_c_round and
> scm_c_truncate so that we can eventually use the names scm_round and
> scm_truncate for the C version of the Scheme procedures round and
> truncate? I think that would be the Right Thing.
I would leave them as they are. The names are unfortunate, but not
actively harmful. Transitions, no matter how long they're spread
over, are always painful and I'd think not worth it in this case.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-09 23:57 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
2004-08-09 23:08 ` Marius Vollmer
2004-08-09 23:57 ` Kevin Ryde [this message]
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=87pt5z27c8.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).