Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #59658
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: FP-Number Ambiguities |
| Date | 2017-05-21 14:59 +0000 |
| Organization | Institut fuer Computersprachen, Technische Universitaet Wien |
| Message-ID | <2017May21.165944@mips.complang.tuwien.ac.at> (permalink) |
| References | <5fa5c564-0e26-4a1b-8236-3d240449b29d@googlegroups.com> <2017May20.125641@mips.complang.tuwien.ac.at> <c9d38aae-76ff-4bd1-9266-cb18161dfd90@googlegroups.com> |
minforth@arcor.de writes:
>Am Samstag, 20. Mai 2017 13:28:56 UTC+2 schrieb Anton Ertl:
>BASE=10 Loaded wordsets:
>INPUT CORE CORE+DOUBLE CORE+FLOAT CORE+DOUBLE+FLOAT
>-------------------------------------------------------------------
>0. not found 0 0 (DPL=0) f: +0. 0 0 (DPL=0)
If we are going to make number conversion for "0." system-dependent,
there is no point in standardizing it. So my vote is for
de-standardizing "0."; doubles can be written as "#0.", and if people
are actually weaned off "0." for doubles (unlikely), we can switch to
having it mean FP at some time in the future.
>1.03 not found 103 0 (DPL=1) f: 1.03 f: 1.03
Again, if "1.03" has a system-dependent meaning, there is no point in
standarizing it. Also, if "1.03" means float, it is confusing if "0."
can mean double in the same system (your last column); i.e., we can
only go there once we have de-standardized "0." as double.
>INF not found not found +INF +INF
Such constants are certainly a good idea as FLOAT EXT words (i.e.,
optional for the sake of soft-float implementations; in hardware, IEEE
has won). Who makes the proposal?
>well-behaving to legacy code
If I load a legacy program containing "1.03" on a system with
CORE+DOUBLE+FLOAT, the program gets a float, while it expects a
double. I.e., not at all well-behaved.
- anton
--
M. Anton Ertl http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
New standard: http://www.forth200x.org/forth200x.html
EuroForth 2017: http://www.euroforth.org/ef17/
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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