From: Dirk Herrmann <dirk@ida.ing.tu-bs.de>
Cc: Guile Bugs <bug-guile@gnu.org>
Subject: Re: Bad deprecation warnings in numbers.c
Date: Mon, 15 Apr 2002 23:42:10 +0200 (MEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0204152338300.24957-100000@marvin.ida.ing.tu-bs.de> (raw)
In-Reply-To: <m3wuvcszq6.fsf@laruns.ossau.uklinux.net>
On 13 Apr 2002, Neil Jerram wrote:
> Dirk> IMO, people should not use any of these functions at all.
> Dirk> We should try to remove their use from other places within
> Dirk> guile as well. The reason is, that these functions depend
> Dirk> on the implementation of the bignums, which should be
> Dirk> considered the secret knowledge of the number
> Dirk> implementation. It is, btw., likely to change in the not
> Dirk> too far future, if for example we manage the switch to the
> Dirk> GNU mp library.
[...]
> If there are no valid reasons for using these functions, we should
> change the messages to say that "this function was never intended to
> be part of the libguile API". (And then the mailing list may later
> produce a valid reason for us! :-)
IMO that's a good way to go.
Best regards
Dirk Herrmann
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-04-15 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-01 15:10 Bad deprecation warnings in numbers.c Neil Jerram
2002-04-02 19:16 ` Dirk Herrmann
2002-04-13 12:44 ` Neil Jerram
2002-04-15 21:42 ` Dirk Herrmann [this message]
2002-04-14 5:11 ` Rob Browning
2002-04-15 21:44 ` Dirk Herrmann
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=Pine.LNX.4.21.0204152338300.24957-100000@marvin.ida.ing.tu-bs.de \
--to=dirk@ida.ing.tu-bs.de \
--cc=bug-guile@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).