> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> Anyone know of a good bigint/bigfloat library whose terms are such
DS> that we can just snag the source and use it in perl? I don't
DS> really care to write the code for division, let alone the
DS> transcendental math ops...
well
At 04:31 PM 12/29/00 +, David Mitchell wrote:
>The current thread about bigints and overflows and stuff has given me
>a thought:
>
>A few of the bits in the flags word of an SV should be reserved as
>part of the payload (as opposed to being generic SV flags), so a particular
>SV type can make
The current thread about bigints and overflows and stuff has given me
a thought:
A few of the bits in the flags word of an SV should be reserved as
part of the payload (as opposed to being generic SV flags), so a particular
SV type can make whatever internal use it likes of them. Ie the
payload a
At 01:15 PM 12/29/00 +, Nick Ing-Simmons wrote:
>Dan Sugalski <[EMAIL PROTECTED]> writes:
> >
> >BigInt and BigFloat are both pure perl, and as such their speed leaves a
> >*lot* to be desired. Fixing that (at least yanking some of it to XS) has
> >been on my ToDo list for a while, but other s
At 01:05 PM 12/29/00 +, Nick Ing-Simmons wrote:
>Dan Sugalski <[EMAIL PROTECTED]> writes:
> >
> >I'm reasonably certain that all platforms that perl will ultimately run on
> >can muster hardware support for 16-bit integers.
>
>Hmm, most modern RISCs are very bad at C-like 16-bit arithmetic - t
At 12:56 PM 12/29/00 +, Nick Ing-Simmons wrote:
>Dan Sugalski <[EMAIL PROTECTED]> writes:
> >
> >Strings can be of three types--binary data, platform native, and UTF-32.
> >No, we are not messing around with UTF-8 or 16, nor are we messing with
> >EBCDIC, shift-JIS, or any of that stuff.
>
>I
Dan Sugalski <[EMAIL PROTECTED]> writes:
>
>BigInt and BigFloat are both pure perl, and as such their speed leaves a
>*lot* to be desired. Fixing that (at least yanking some of it to XS) has
>been on my ToDo list for a while, but other stuff keeps getting in the
>way... :)
My own "evolutionary
Dan Sugalski <[EMAIL PROTECTED]> writes:
>
>I'm reasonably certain that all platforms that perl will ultimately run on
>can muster hardware support for 16-bit integers.
Hmm, most modern RISCs are very bad at C-like 16-bit arithmetic - they have
a tendency to widen to 32-bits.
>I also expect th
Dan Sugalski <[EMAIL PROTECTED]> writes:
>
>Strings can be of three types--binary data, platform native, and UTF-32.
>No, we are not messing around with UTF-8 or 16, nor are we messing with
>EBCDIC, shift-JIS, or any of that stuff.
I don't understand that in the light of supporting "platform n
