I love that they put "usually" in this sentence:
"Humans usually are not as good writing machine code as they are at writing Fortran"
--
About GNU Fortran
https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gfortran/About-GNU-Fortran.html
Is there sb. out there working with the GNU #FORTRAN compiler and may be able to help me with buffered/unbufferd I/O issues?
#gfortran #help #gcc #ancientcode
#fortran #gfortran #help #gcc #ancientcode
@neilernst
There is of course a lot of debate in the #Fortran community to get rid of that. No one would of course use implicit typing in modern code, but legacy codes are still running in many libraries...
But implicit typing is still officially the default, and IMPLICIT NONE must be used in every code.
Compilers are also of course offering options like -fimplicit-none in #GFortran. But putting explicitly IMPLICIT NONE in code is a better practice! :-)
You can try #Fortran with online #compilers:
- On the Fortran Playground https://play.fortran-lang.org/ you can learn Fortran by compiling (and editing) various examples.
- On Godbolt Compiler Explorer https://godbolt.org/, you can use several versions of #GFortran, Intel #ifort, Intel #ifx and #Flang. And you can read the assembler code.
- On https://dev.lfortran.org/ you can play with the #LFortran compiler (development in progress) and see its intermediate representations.
#lfortran #flang #IFX #ifort #gfortran #compilers #FORTRAN