bugAxiom Computer Algebra System - Bugs: bug #9424, Bug in handling 0^0 in Axiom

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #9424: Bug in handling 0^0 in Axiom

Submitter:  David MentrĂ© <dmentre>
Submitted:  Tue 22 Jun 2004 04:53:36 PM UTC
   
 
Category:  algebra Severity:  3 - Normal
Item Group:  code bug Status:  transferred
Privacy:  Public Assigned to:  None
Originator Name:  David MENTRE Open/Closed:  Open
Release:  Reproducibility:  Every Time
Fixed Release: 
Error message: 


Example of code trigerring the bug: 

0::CARD ^ 0::CARD
-- should return 1::CARD
complex(0,0)^complex(0,0.0)
-- should return '0**complex(0,0.0)' is undefined
complex(0,0)^complex(2,2.0)
-- should return complex(0,0)

Internal cause: 


Tue 22 Jun 2004 04:53:36 PM UTC, original submission:  

After a long thread on axiom-developer, the following concensus was optained:

Page, Bill writes:
 > On Tuesday, June 22, 2004 6:11 AM Martin Rubey
 > -email is unavailable- wrote:
 >
 > There is a bug.
 >
 >   0::CARD ^ 0::CARD
 >
 > should be 1::CARD

ok.
 
 > > except that in
 > >
 > > Vanuxem Grgory writes:
 > > > In complex(Float) and Complex(SingleFloat), we have to change the
 > > > exponentiation so that
 > > >         complex(0,0)^complex(0,0.0)
 > > > or
 > > >         complex(0,0)^complex(2,2.0)
 > > > doesn't use log.
 > >
 > > the latter really should give 0?
 > >
 >
 > No. complex(0,0)^complex(0,0.0) is like 0^0.0 and should
 > return
 >
 >   '0**complex(0,0.0)' is undefined
 >
 > The message 'log 0 generated' is confusing but technically
 > correct.

Yes, but complex(0,0)^complex(2,2.0) should be 0.0, shouldn't it?

David Mentré <dmentre>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

 

Follow 2 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-01-03 billpage1 ReproducibilityNone Every Time
2006-01-03 billpage1 StatusNone transferred

Back to the top

Powered by Savane 3.13-5190.
Corresponding source code