[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bad deprecation warnings in numbers.c

From: Rob Browning
Subject: Re: Bad deprecation warnings in numbers.c
Date: Sun, 14 Apr 2002 00:11:51 -0500
User-agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.2 (i386-debian-linux-gnu)

Dirk Herrmann <address@hidden> writes:

> IMO, people should not use any of these functions at all.  We should
> try to remove their use from other places within guile as well.  The
> reason is, that these functions depend on the implementation of the
> bignums, which should be considered the secret knowledge of the
> number implementation.  It is, btw., likely to change in the not too
> far future, if for example we manage the switch to the GNU mp
> library.

FWIW I've got GMP bignum's working here :> Guile passes make check,
but I've still got a lot of FIXMEs and #warnings to repair.

IMO, scm_i_mkbig probably shouldn't be used by user code and shouldn't
even be in numbers.h unless (as is the case ATM) other libguile code
needs to call it.  (The only way around that I can think of would be
go to a "public/private" header arrangement.)

However, a function like 

  void scm_num2mpz(mpz_t dest, SCM src);

(or similar) might not be a bad idea.  We could continue to provide it
in libguile or in a helper lib indefinitely, no matter what our
internal representation is.

Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

reply via email to

[Prev in Thread] Current Thread [Next in Thread]