Re: 8.5 docs: no "in" description

Keith Vetter wrote:
At least in 8.5, tcl_precision has been deprecated. See tip 132.

At least in 8.5, Tcl now does The Right Thing when converting a
floating point number to a string. You probably wouldn't believe how
insanely difficult this is to do (if you do know, you'll be more
impressed still...)

Donal.

.

Relevant Pages

  • Re: Precision problem
    ... > so that i am converting it to string using gcvtand sprintfetc. ... > After this some precision loss is happening. ... floating point value that's turning out different from your expectations, ...
    (microsoft.public.vc.mfc)
  • Re: Precision problem
    ... > so that i am converting it to string using gcvtand sprintfetc. ... > After this some precision loss is happening. ... floating point value that's turning out different from your expectations, ...
    (microsoft.public.vc.language)
  • Integers have docstring for int()
    ... docstrings that describe the functions to create them. ... A floating point\nargument will be truncated towards zero (this does not i ... string, use\nthe optional base. ... It is an error to supply a base when converting ...
    (comp.lang.python)
  • Re: Floating point arithmetic support in DCL
    ... >> However, why all this stuff about holding the floating point value as a string, ... > converted to a string for display or concatenation to a string etc. ... Converting from latitude to ...
    (comp.os.vms)
  • Re: I think a problem occured when i used long()
    ... | Convert a string or number to a long integer, ... | string representation of a floating point number!) ... | converting a non-string. ... So, converting a float to an integer should really truncate the result, ...
    (comp.lang.python)