For some reason, raising a real number to some power gives a less accurate result in Fortran than does manually typing out each multiplication individually.
By which I mean T*T*T*T*... (until you have typed n Ts) is more accurate than T**n (that's T^n).
The wonders of computers.
@serfdeweb
YES! I actually have a copy of the #FORTRAN source on paper tape of that somewhere around the house.
#games #retrogaming #StarTrek
New post: https://jcarroll.com.au/2025/06/29/counting-digits-quickly/
What if you could just wave a magic wand over your R #rstats 
code and have it transform into something that ran as fast as or faster than C? @t_kalinowski's {quickr} 'R to Fortran Transpiler' does that for you! #fortran
With bonus comparisons to #Rcpp #julialang 
and #rustlang 
Updated to restrict to integers thanks to @toddixd
Just spent half an hour chasing an error which resulted in my code giving answers that are a fraction of an arcsecond off. Turns out that, for some reason, exponentising reals can cause loss of precision in Fortran 
Once again Wolfram Alpha proves its incredible usefulness.
Things I learned yesterday and today.
Python doesn't understand quadruple-precision real numbers. f2py will happily compile Fortran code containing real(16)s into a form that Python can talk to, but Python will segfault as soon as it receives one of those real(16)s.
Also, Fortran's built-in fraction function doesn't do what I thought it did.
Back to the Fortran Future 2
This satellite event takes place 8th September 2025 adjacent to RSECon25 (9-11th September 2025) at the University of Warwick.
Its free to attend, so if you have an interest in Scientific Fortran please consider joining us.
@muzej I used this as my first programming manual: https://plus.cobiss.net/cobiss/si/sl/bib/16922 #fortran
Hold on, f2py CAN make Fortran functions comprehensible to Python‽ I DON'T have to use subroutines‽ Fortran syntax is just incredibly FUSSY‽
FORTRAN IV Manual (1982), adapted by Rafko Adrinek and published by Iskra Delta! 
#FORTRAN was the first widely adopted “standard” programming language, especially popular during the 1960s and 70s — the punch card era. 
Back then, it powered massive mainframes, and its legacy still lives on today in modern supercomputer programming! 
Only programmers and The binding of Isaac players will understand
#thebindingofisaac #game #rougelike #programming #code #languages #levels #python #scratch #ruby #js #java #csharp #c #c++ #cobol #fortran #assembly
I have figured out the correct syntax to make floating-point calculations in Fortran more precise.
Tänään olen lukenut Otto Mannista ja oppinut laskemaan keskiarvon nykyaikaisella #Fortran'illa (tai jos tarkkoja ollaan, oppinut lukemaan sillä vakiosyötevirtaa niin, että ohjelma osaa siivosti lopettaa lukemisensa tiedoston loppuun). #runot #OttoManninen #ohjelmointi #miehenelämää #kotijuttuja
So now one of the reasons for GNU #FORTRAN is gone:
Keep hearing whispering voices "GNU COBOL, GNU COBOL"
@mattgemmell Surely you mean 64x16.
Yes, that is Fortran. On the Radio Shack TRS-80. My first programming job.
I would be a greybeard #UNIX guy if I could grow a non-scraggley beard, and it's unfair to the #DOGE teens to claim that the IRS and Social Security rely on ancient #COBOL code that only a few people alive actually understand. They also rely on ancient #FORTRAN code and even I never studied that at Computer Camp.
The original #LISP had 7 primitives: \(\texttt{cons}\), \(\texttt{car,}\) \(\texttt{cdr}\), \(\texttt{atom}\), \(\texttt{quote}\), \(\texttt{eq}\), and \(\texttt{cond}\). And the original #Smalltalk syntax could fit on a 5×7 card. That meant a novice could learn the syntax in a matter of minutes, and direct all his efforts to learning how properly to wield the power of that Turing-complete language. This was why, in the 1970s and the 1980s, many college freshmen were taught FP in Scheme (a more modern LISP) and many middle school children were taught OO in Smalltalk. These were surely the best "first" #programming languages.
#FORTRAN and #BASIC were simple, too. FORTRAN, the first high-level language, has been in continuous use since the late 1950s by engineers, who are not keyboard warriors. BASIC was invented in the early 1960s for teaching programming to non-STEM students at Dartmouth. It sired a whole generation of self-taught children in the 1980s.
Compare those to C++, Erlang, Python, Haskell, Java, JavaScript, Scala, Rust, Kotlin, and pretty much every language in popular use today. Most consider Python and JavaScript to be the simplest of modern languages. Yet, they are massive, complex languages. No 10-year-old could teach himself those, nor should he.
The original versions of those classic languages cannot be used to solve modern problems. But they should still be taught to youngsters as their first language. Throwing in the kids' faces a modern enterprise language confuses them and discourages them. Consequently, many novices never attain that state of flow, when the joy of programming gushes forth.
#Simplicity is a virtue.
Writing a commandline tool in #Fortran:
https://www.draketo.de/english/free-software/fortran
In case you want to broaden your #programming skills. Fortran seems to be making a comeback (currently 11 in the Tiobe index: https://www.tiobe.com/tiobe-index/fortran/ ).
This is from 2017, written at the end of my Physics PostDoc where I used quite a bit of Fortran and learned to appreciate it much more than I expected.
ѦਹѤʞ 
