On Sat, Apr 12, 2008 at 2:53 PM, Jason Grout <[EMAIL PROTECTED]> wrote: > > In working on #2898, I discovered that for Python, int(NaN) is 0.
Wow that is nasty. Of course, in Python int(1.5) is 1, which is kind of disturbing too. > Using > RR and Integer (properly, in my opinion) throws an exception for > Integer(RR(0.0/0.0)). > > For RDF, should we make special cases for an RDF that is NaN when doing > operations that involve converting to an integer? Or, in the interest > of speed, should we just follow the Python convention? I would definitely make Integer(RDF's NaN) throw an error. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
