On 3/28/07, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
> This was actually all a footnote to the main question of the original
> post, namely having an UnparsedLiteralDecimal class used by the
> preparser to avoid awkwardness like
>
> sage: RealField(100)('1.2') == RealField(100)(1.2)
> FalseI'm all for it. In fact, if it were up to me RealNumber would only have one constructor: mpfr_from_str() (or something like that) so that numbers are represented as accurately as possible. My thinking is that: -- If I wanted simple doubles, I would be using python floats anyway. -- why specify a "precision" if something like RealField(100)(1.2) is only going to be accurate at the first 53 bits? didier --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
