Re: bug in bigint?

I've poked through my copies of calc.pm and bigint.pm. The offending routine is _log_int (I'm sure you knew that) which requires 2 arguments (the number and the base to which the log is to be taken; I'm sure you knew that, too). It's called from blog in bigint.pm, without the second argument.

I'd agree that this is a bug.

I also noticed that

#!perl

use strict;

use warnings;

use bignum;

my $n = -1;
print 10.00 **$n  . "\n";
[download]

returns NaN (on Windows; ) for negative values of $n. However, Math::BigFloat works.

emc

At that time [1909] the chief engineer was almost always the chief test pilot as well. That had the fortunate result of eliminating poor engineering early in aviation.

—Igor Sikorsky, reported in AOPA Pilot magazine February 2003.

Comment on Re: bug in bigint? Download Code

Replies are listed 'Best First'.
Re^2: bug in bigint? by blazar (Canon) on Dec 01, 2006 at 18:59 UTC
The offending routine is _log_int (I'm sure you knew that) which requires 2 arguments (the number and the base to which the log is to be taken; I'm sure you knew that, too). Actually you are wrong... being sure I knew. In fact I didn't. I suppose it would have been easy to know. But I wasn't extremely interested, just stumped into this, and felt like reporting. I was quite confident this may be a real bug of the module, for once (generally a perceived bug), but preferred discussing the issue here. I'll report it to the author as well.	[reply]

Replies are listed 'Best First'.

Re^2: bug in bigint?
by blazar (Canon) on Dec 01, 2006 at 18:59 UTC

The offending routine is _log_int (I'm sure you knew that) which requires 2 arguments (the number and the base to which the log is to be taken; I'm sure you knew that, too).

Actually you are wrong... being sure I knew. In fact I didn't. I suppose it would have been easy to know. But I wasn't extremely interested, just stumped into this, and felt like reporting. I was quite confident this may be a real bug of the module, for once (generally a perceived bug), but preferred discussing the issue here. I'll report it to the author as well.

[reply]