Front page | perl.perl5.porters |
Postings from March 2001
Re: [PATCH] Re: Math::Big* v1.21
Thread Previous
|
Thread Next
From:
Jarkko Hietaniemi
Date:
March 31, 2001 07:40
Subject:
Re: [PATCH] Re: Math::Big* v1.21
Message ID:
20010331094024.C8991@chaos.wustl.edu
> Yes, that is what was my plan/wishfull dreaming ;o) I am working hard to
> make it a true (aka working the same as closely as possible) replacement.
>
> Unfortunately, Math::BigFloat is not ready yet, so you probably don't
> want to include it. The old Math::BigFloat is not working with the new
> Math::BigInt since it relies on to many internals.
>
> I am working hard to get M::BF complete. Sorry that it is not ready yet.
>
> > Yes, licensing has been an issue in the past. Basically, if the
> > licensing is anything else than the Perl dual Artistic/GPL, there's
> > a problem.
>
> I think in the future we get Bit::Vector as the underlying library, and
> this means more speed (C!) and no licencing issues, since thats a perl
> module (thanx to Steffen Beyer for his work!). But this means more work for
> me and Bit::Vector must be included too. Hm. Wel, we leave that for later.
>
> > How big is the new Math::Big*?
>
> 70 kb compressed, but thats including all the Math::String etc. about 40
> KByte for M::BI.pm. (its pure Perl)
>
> As soon as it is ready for inclusion (determined by you or me) I will strip
> the other Math::String stuff and make them an extra CPAN module.
>
> Maybe it is time to collect all the pure-Perl math stuff and check if it
> still working. I will look at Math::Fraction, since my Math::BigFraction is
> reinventing the wheel there. I haven't heard back from the original author,
> though.
When both the M::BI and M::BF really are available are true drop-in
replacements, that is, backward compatibility with the pure-Perl
add-ons has been checked, I might consider including it. The
extension is more than a bit on the large side, though, that might
be a serious problem. Bignums, especially bigints, are nice to have,
but essential, so one must weight the costs carefully.
One area of completely unexplored area of work that might be useful
would be for someone to research the various available bignum
libraries and figure out how integrate the support of those into the
core language. I'm not talking about having separate extensions for
each bignum library out there because there are too many, what I'm
after is some kind of more transparent support for 2**1000.
> Attached is a patch for perlop.pod against @9424:
Thanks, will apply.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
Thread Previous
|
Thread Next