I disagree. Yes, there are situations where 0^0 should be undefined, but there are also several cases where it should be 1. Given that, I don't want my numerical methods package to be crashing all the time because Perl thinks it should be undef.
in reply to Re: 0**0
in thread 0**0
The fact is, the coder should know which case he is interested in (1 or undef as the answer); I think it is better from a coding perspective to check for the undef case, and just allow the 0^0 == 1 case without special checking.
Now, who the heck is writing numerical methods packages in Perl--FORTRAN is the way to go :-)
Project coordinator of the Generic Model Organism Database Project