bugAxiom Computer Algebra System - Bugs: bug #9313, 0^0 handled inconsistently

 
 

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

bug #9313: 0^0 handled inconsistently

Submitter:  Martin Rubey <kratt6>
Submitted:  Sat 12 Jun 2004 05:20:11 PM UTC
   
 
Category:  None Severity:  3 - Normal
Priority:  5 - Normal Item Group:  code bug
Status:  Duplicate Privacy:  Public
Assigned to:  None Originator Name:  kratt6
Open/Closed:  Closed Release:  tla june 2004
Reproducibility:  None Fixed Release: 
Error message: 


Example of code trigerring the bug: 

0^0

Internal cause: 

The reason for 0^0 giving 1 is that axiom uses the lisp function expt for exponentiation of integers, which returns 1 (which is in line with the common lisp hyperspec)

Discussion

Wed 30 Jun 2004 07:11:25 PM UTC, comment #2: 
[Added information or comment]

This is not a bug but is related to bug #9424

See following message for details.
http://lists.nong ... -06/msg00250.html

David Mentré <dmentre>
Group administrator
Wed 30 Jun 2004 07:10:51 PM UTC, comment #1: 
[Added information or comment]

This is not a bug but is related to bug #9424

See following message for details.
http://lists.nong ... -06/msg00250.html

David Mentré <dmentre>
Group administrator
Sat 12 Jun 2004 05:20:11 PM UTC, original submission:  

mathematically speaking, 0^0 should be undefined. However, in axiom there are different kinds of 0^0, depending on the type of 0:

(1) -> 0^0
   (1)  1 Type: PositiveInteger
(2) -> 0^0.0
   >> Error detected within library code:
   0**0 is undefined

protected-symbol-warn called with (NIL)
(2) -> 0.0^0
   (2)  1.0 Type: Float
(3) -> 0.0^0.0
    >> Error detected within library code:
   0**0 is undefined

protected-symbol-warn called with (NIL)

Martin Rubey <kratt6>

 

Attached Files

This item currently has no attached files.

 

Dependencies

This item does not depend on any other items.

No items depend on this one.

 

Mail Notification Carbon-Copy List

 

Votes

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.

 

History

Follow 2 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2004-06-30 dmentre Open/ClosedOpen Closed
2004-06-30 dmentre StatusNone Duplicate

Back to the top

Powered by Savane 3.16-ed84.
Corresponding source code