Bill Allombert on Mon, 18 Dec 2023 00:14:29 +0100
|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
Re: libpari precision handling changes
|
- To: pari-dev@pari.math.u-bordeaux.fr
- Subject: Re: libpari precision handling changes
- From: Bill Allombert <Bill.Allombert@math.u-bordeaux.fr>
- Date: Mon, 18 Dec 2023 00:14:23 +0100
- Delivery-date: Mon, 18 Dec 2023 00:14:30 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=math.u-bordeaux.fr; s=2022; t=1702854865; bh=Nyh/H/hOsD7zVjgXYvmj+AYmSlKBgBd5kg+gd1tznks=; h=Date:From:To:Subject:References:In-Reply-To:From; b=jy2oUKT6RnDfoBFfrqfArjIRHJj3xEok/M+bjBQMisivqzAzO0jdysHwcCxfsYGT3 VG7c9tparzDlziBHZBKIf+zGnzB+LsJqi6mXgmBXqdkuzlRA/BU64U4ei9C4lw0Bxw aqekIX/ovDq0yt1pwuaWqTiUzWbsRQoXA4wFX8j6RXTqT2LmUhW8hd9BI4CRmFAeps Ffd7e/tPw5hY8mXZqSp+Y3vH/sa1xejUYj4FAaCMgeFrLtXYyjEou/BSER9HOk2fwb pIkWdasLgre5vvSalZ0DMsZfpxNf/1XZbGouPyXrYFdpsXO9Qyc4l6KtNMpbcVghAw LeJw1CT4hMvxfATrxQ/uYfu1l4SB61liEWRW8DPAvQlyQT0lhtEBq9TqZZhlKCBHC8 Ypn8+NsXmPdPmlc63kIDJcbF8bi8xh1jfRus3UIQzoUncPdTzgqh8uzq0zjNGre78o C4TXU/pUF252Uq5Cp//lclYVOS5lqg0k7/uxGNz/V8mtF2XPuPDJwFtvJnLKGtbWc2 h2J5o23IuBzzK9hPyPuMux5oIG060KSHMhW346T7XEDGM1qnJrVVctexCPiuraKg+P CouNJIr1KbYSfVO57meu4YA8W7T0B++a5untSfvsWVNGxbXDYXW/8IllDdrWUWDbC9 H+DyUnyWyAcf7R/FOJHOUp3g=
- In-reply-to: <ZXuwiTdvUFVzsaAy@login.math.berkeley.edu>
- Mail-followup-to: pari-dev@pari.math.u-bordeaux.fr
- References: <ZWzqp8+Qz9wvZ2jU@seventeen> <ZXuwiTdvUFVzsaAy@login.math.berkeley.edu>
On Thu, Dec 14, 2023 at 05:48:57PM -0800, Ilya Zakharevich wrote:
> On Sun, Dec 03, 2023 at 09:52:55PM +0100, Bill Allombert wrote:
> > Dear PARI developers,
> >
> > I committed a change to the way the precision is manipulated in the
> > C library.
> >
> > Now the precision is a multiple of BITS_IN_LONG.
>
> Is not there the code 'b' for this? Why not use it?!
It is not the same. 'b' allows any number of bits, while 'p' allows only multiple of
BITS_IN_LONG. This is necessary until we allows t_REAL with precision in bits.
Cheers,
Bill