... to legitimise the usage of data declarations of the form REAL*8, ... in active use which uses REAL*8 etc, and in such programs this ... they ought to write something like ? REAL(KIND=SELECTED_REAL_KIND(15,99)) variable ... if the largest amount of cpu time used by Fortran progranms is not...Brian Salter-Duke � � � � �Melbourne, Australia � � My real address is b_duke(AT)bigpond(DOT...

...to legitimise the usage of data declarations of the form REAL*8, INTEGER*2 etc I'm fully aware...in active use which uses REAL*8 etc, and in such programs ... ought to write something like ? REAL(KIND=SELECTED_REAL_KIND(15,99)) variable ... the largest amount of cpu time used by Fortran progranms is ... Salter-Duke Melbourne, Australia My real address is b_duke(AT)bigpond(...

...agree that it �may be time to legitimise the usage of data declarations of the form REAL*8, ...in active use which uses REAL*8 etc, and in such programs this...they ought to write something like � REAL(KIND=SELECTED_REAL_KIND(15,99)) variable ...All current compilers seem to accept REAL*8 and similar without problems for... a floating point variable occupying 8 bytes. or 2) Reject the ...

... agree that it  may be time to legitimise the usage of data declarations of the form REAL*8, INTEGER*2 etc I'm fully aware ... in active use which uses REAL*8 etc, and in such programs this ....  Unfortunately the simplest change: altering   REAL*8 variable to   DOUBLE PRECISION variable ... they ought to write something like   REAL(KIND=SELECTED_REAL_KIND(15,99)) variable ...

...Fortran still in active use which uses REAL*8 etc, and in such programs this is the major (sometimes the only)...'t think I have got many converts. Unfortunately the simplest change: altering REAL*8 variable to DOUBLE PRECISION variable I suppose I agree, REAL*8 as a synonym for DOUBLE PRECISION ...'t just backspace.) There are compilers now that accept REAL*8 but not REAL*4....

... active use which uses REAL*8 etc, and in such programs ... ought to write something like REAL(KIND=SELECTED_REAL_KIND(15,99)) variable ...see the usage of REAL*8 legitimised. I find the kind...and *all* my generically defined reals and complex's switch between...found it *extremely* difficult and time-consuming to produce really general...I'd rather spend my time doing interesting stuff *using* these...

... agree that it may be time to legitimise the -|usage of data declarations of the form REAL*8, INTEGER*2 etc -| -|I'm fully aware ... in active use which uses -|REAL*8 etc, and in such programs this .... Unfortunately the simplest change: altering -| REAL*8 variable -|to -| DOUBLE PRECISION variable ... they ought to write something like -| REAL(KIND=SELECTED_REAL_KIND(15,99)) variable -|...

...agree that it may be time to legitimise the usage of data declarations of the form REAL*8, ...in active use which uses REAL*8 etc, and in such programs this.... Unfortunately the simplest change: altering REAL*8 variable to DOUBLE PRECISION variable...they ought to write something like REAL(KIND=SELECTED_REAL_KIND(15,99)) variable ...that on a byte-oriented machine REAL*8 is a more concise ...

... might well do it in all 6000 cases of REAL*8 occuring. The change has already been made in some codes such as GAMESS(US), but there ... such processing causes to extend beyond the 72 column limit may be made into a continuation: REAL*8 abc, def, ..., xyz becomes: REAL(dp) :: abc, def, ... pqr, & stu, vw, xyz If the ...

... compilers. However, as I have said, conversion of REAL*8 to DOUBLE PRECISION is trivial, without producing long lines. As I indicated earlier I ... standard, but I do support keeping compilers backwardly compatable with F77 and allowing REAL*8. I can't figure out what the alarm is about; when's the last time any compiler removed such a feature, or a ...