----------------------------------------------------------------------------------
@MSGID:
f538c215
@REPLY:
<3cb57395-be28-4451-9e98-c20ed41386fbn@googlegroups.com> 146f6379
@REPLYADDR pehache <pehache.7@gmail.com>
@REPLYTO 2:5075/128 pehache
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
@RFC-References:
<873f9cc4-6139-4bd3-9ed8-de7e37a76730n@googlegroups.com> <d24b9f27-36da-4011-963d-eba713b1f16an@googlegroups.com>
<3cb57395-be28-4451-9e98-c20ed41386fbn@googlegroups.com>
@TZUTC: 0000
@PID: Nemo/0.999a
@TID: FIDOGATE-5.12-ge4e8b94
Le 28/08/2023 ? 02:45, Kim Hanjoon a ?crit :
> Thank you! I have never expected fortran`s default precision is float not
> double.
The default precision is the one of the REAL type, nothing more. The
standard does not specify the actual size and precision of this type.
Although it is nowadays mapped to the IEEE754 single precision 32 bits
floating point by most (if not all) compilers, it was not the case in the
past. Notably, on the CRAY machines it was mapped to the hardware native
64 bits floating point.
But mapping the REAL type to 64 bits had an important drawback back then :
it was impossible to propose a 32 bits type in a portable way, as the
standard was only requiring the REAL type, and the DOUBLE PRECISION type,
which had to be twice the size of the REAL type.
--- Nemo/0.999a
* Origin: Nemoweb (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441