Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.forth > #59798

Re: FP-Number Ambiguities

Show all headers | View raw

minforth@arcor.de wrote:
> Am Mittwoch, 24. Mai 2017 09:21:49 UTC+2 schrieb HAA:
> > minforth@arcor.de wrote:
> > > ...
> > > 0 set-precision  ok  <-- test if this trims
> > > 1e fs.  .  <-- gforth hangs
> >
> > PRECISION under ANS refers to 'significant digits' (see the spec).
> > Displaying zero significant digits is meaningless i.e. an ambiguous condition.
> > Similarly ambiguous is requesting more significant digits than your system
> > can supply.   With this in mind, most forths range-limit SET-PRECISION
> > e.g. 1 MAX  xxx MIN  where xxx is the highest precision the system can supply,
> > say 16 for 64-bit floats.
> >
> > Perhaps you are thinking of 'decimal places'?  ANS has nothing to say about
> > that.  Your system may provide suitable functions or you can write your own.
>
> Sure I know, garbage in, garbage out.
> Anyhow the fp-number wordset spec is short and leaves many things "system specific".
> Also whether trailing zeros are significant or not so that they can be trimmed
> is "application specific".
> ...

Much water has passed under the bridge since ANS.  IMO it's no longer a case
of what did ANS mean, but has it fulfilled the expectations of f/p users.  I expect
f/p output functions similar to what C and Fortran offer and today there are Forths
which provide that.  Do they care whether they conform to ANS?  I suspect not.

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

FP-Number Ambiguities minforth@arcor.de - 2017-05-19 14:06 -0700
  Re: FP-Number Ambiguities anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-20 10:56 +0000
    Re: FP-Number Ambiguities minforth@arcor.de - 2017-05-20 11:50 -0700
      Re: FP-Number Ambiguities anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-21 14:59 +0000
        Re: FP-Number Ambiguities minforth@arcor.de - 2017-05-21 12:08 -0700
          Re: FP-Number Ambiguities mhx@iae.nl - 2017-05-21 12:50 -0700
            Re: FP-Number Ambiguities minforth@arcor.de - 2017-05-21 15:04 -0700
          Re: FP-Number Ambiguities anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-22 11:43 +0000
            Re: FP-Number Ambiguities minforth@arcor.de - 2017-05-22 06:40 -0700
              Re: FP-Number Ambiguities albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-05-22 16:33 +0200
                Re: FP-Number Ambiguities minforth@arcor.de - 2017-05-22 08:34 -0700
              Double numbers and floats in the text interpreter (was: FP-Number...) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-22 16:17 +0000
    Re: FP-Number Ambiguities pahihu <pahihu@gmail.com> - 2017-05-24 10:19 -0700
      Re: FP-Number Ambiguities minforth@arcor.de - 2017-05-24 11:21 -0700
        Re: FP-Number Ambiguities pahihu <pahihu@gmail.com> - 2017-05-24 12:13 -0700
          Re: FP-Number Ambiguities minforth@arcor.de - 2017-05-24 13:12 -0700
  Re: FP-Number Ambiguities (answer imported from future) Jan Coombs <jenfhaomndgfwutc@murmic.plus.com> - 2017-05-20 22:54 +0100
  Re: FP-Number Ambiguities "HAA" <someone@microsoft.com> - 2017-05-24 17:21 +1000
    Re: FP-Number Ambiguities minforth@arcor.de - 2017-05-24 01:11 -0700
      Re: FP-Number Ambiguities "HAA" <someone@microsoft.com> - 2017-05-25 12:28 +1000
        Re: FP-Number Ambiguities minforth@arcor.de - 2017-05-25 00:36 -0700

csiph-web