Re: Is it time to legitimise REAL*8 etc?

Richard Maine wrote:
Paul van Delst <Paul.vanDelst@xxxxxxxx> wrote:

Could someone explain to me the cumbersomeness of
SELECTED_REAL(INT)_KIND() ??
I agree the syntax is a bit wordy,

Yes, that's one thing - one that I think is more important than you make
it out to be. Another is that it just doesn't match the way most people
want/need to specify things. Decimal digits of precision might seem fine
in theory, but that just isn't a good match the reality of programming.
When what you want to do is select between the 32-, 84- and 128-bit
options for real, it is cumbersome to translate that into numbers of
decimal digits.
> ...[rest of most excellent post elided for brevity]...

Thanks for filling in what I would undoubtedly have tried to say far less distinctly... :)

I was wishing I had used (or added) "obtuseness" as opposed to simply cumbersome as it is what I find particularly the most difficult issue, indeed.

On a given set of hardware, one learns what it means rather quickly and there are a relatively limited number of options of practical application. But, then one is back to the example I gave before where the shorthand route is probably just as effective for the purpose.

--
.

Relevant Pages

  • Re: Gentler Decimal Floating-Point
    ... or really to specify decimal arithmetic. ... that the range, precision, or scale factor is specified in decimal ... precision in decimal digits for binary arithmetic. ... The language rules specify how those conversions are to be ...
    (comp.arch.arithmetic)
  • Re: Is it time to legitimise REAL*8 etc?
    ... want/need to specify things. ... Decimal digits of precision might seem fine ... but that just isn't a good match the reality of programming. ...
    (comp.lang.fortran)
  • Re: example of KIND to replace DOUBLE PRECISION
    ... I thought that single precision on 32-bit cpu's ment 13+ safe digits, ... specified number of significant decimal digits or exponent range. ... specify that with SELECTED_REAL_KIND and use the appropriate ...
    (comp.lang.fortran)
  • Re: KIND defined in bits and bytes?
    ... a KIND defined in decimal digits uses 4 bytes. ... This is not a function of what units you use to specify ... If the compiler supports an integer representation that uses 3 ...
    (comp.lang.fortran)
  • Re: about c to fortran
    ... > more than 16 significant figures of precision. ... Where d is the number of decimal digits you write and ... no deficiencies and the other way is to make it so complicated ...
    (comp.lang.fortran)