|
According to Wikipedia, the first comefrom dates back to 1973.
My first encounter with comefrom was in the Babbage programming language, from 1981 (Babbage - The language of the future[^]). Babbage has a lot of other nice features, such as the 'conditional threat statement: DO so and so OR ELSE; For function calls, you have not only call by value and call by reference, but also call by long distance. For case switches, it has the BRIEF CASE statement to encourage portable programming.
A few years ago, I needed programmatic access to the backtrace in an exception handler (maybe there were libraries to do it, even at that time, but I found none, and it wasn't that much work doing it myself). 'ComeFrom' was an obvious name for the stack traversal routine, to show where execution came from when walking into the code causing the exception.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
Nothing wrong with that Richard 
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
|
Seems you are not quite up to date if you are making such statements.
And thus don't know the difference between FORTRAN and Fortran... 
|
|
|
|
|
Old timers Fortran programmers are retiring and need replacements.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
Maybe they can become trainers, coaches. Income after retirement.
|
|
|
|
|
The problem with that is, whoever of the old gurus said (in the 1970s): 'I don't know what languages will look like in year 2000, but they will be called Fortran!'
Fortran 2023 has very little to do with the Fortran I learned in my studies in 1978-83. (Fortran was limited to the first two years.) I do not recognize today's Fortran as anything even vaguely resembling what I learned back then. If I were to teach it, I would first have to learn it as a new language.
Is GOTO at all a relevant statement in modern Fortran?
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
Agree.
As I remember, FORTRAN 90, which I came across in the late 90's had the concept of Pointers. Today's FORTRAN may even have the concept of Classes. And the GOTO may be like "Hey GOTO, GO AWAY FOREVER".
|
|
|
|
|
Yes, it's good to know  .. and the comment on their page adds some reasonable explanation:
"... Less than half a year ago, the new ISO Fortran 2023 definition was published. ... Fortran appears to be fast, having native mathematical computation support, mature, and free of charge. Silently, slowly but surely, Fortran gains ground. It is surprising but undeniable. ..."
So, it's time to find my Fortran FFT code which I used back then ...
modified yesterday.
|
|
|
|
|
From what I've heard, its the NAG, the UK-based Numerical Algorithms Group, which has mainly been responsible for the continued usage of Fortran.
|
|
|
|
|
I would guess it has to do with supercomputers in large part. Fortran has been used with them for decades and still is. Nvidia has support for CUDA in Fortran and that makes it possible to adapt code to run on GPUs which almost every modern supercomputer has these days.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Quote: I would guess it has to do with supercomputers in large part.
That's possible indeed ... Perhaps surprisingly, there is a lot of up-to-date information, for example Fortran - Wikipedia, it makes me also think about possible use in LLM training ...
|
|
|
|
|
'mother tongue' for me as well.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
When I learned C I forgot Fortran, and was happy!
|
|
|
|
|
I had a class in C and FORTRAN in 87/88. I already knew FORTRAN, and I took it mostly for the C.
The teacher tortured us by assigning programs to be solved in the language least suited to solve the problem.
Write some numerical algorithm in C( not FORTRAN ).
Write some parsing and word counting code in FORTRAN(not C)
Kind of proved the point that you can solve any problem with any language.
|
|
|
|
|
Can we compare this with filling a round hole with a square peg? Only that the hole and peg are made of somewhat flexible rubbery material.
|
|
|
|
|
1971 1st year university Computer Science - FORTRAN IV on an IBM 360 with the WATFOR compiler which later became WATFIV. Punched cards and IBM golfball terminals.
Then onto IBM 370 then onto CDC 7000 series all with FORTRAN IV. All this mixed with COBOL, PL/1 and assembler.
Currently working with C# and thinking about learning Angular
|
|
|
|
|
I thought I'd need a card puncher to write true Fortran ...
(remembering that dangerous type of stack)
|
|
|
|
|
I have been writing Fortran since 1989 and have never used a punched card (or tape)
|
|
|
|
|
Around 1980 we had to use the puncher in my first Fortran class in the university.
Later I bought a Z80-PC with an 8" floppy - what a progress!
|
|
|
|
|
IBM 026 card punch machines and Olivetti teletypes producing blue paper tape where my starting point. Still have some original, unpunched, Fortran Statement cards kept as a souvenir.
|
|
|
|
|
I remember, when I studied at the Indian Institute of Science, in Bengaluru, India, in the early 90's, our lab had a big stack of (unpunched) punch cards. I have kept a few of them as a souvenir.
|
|
|
|
|
I remember having to modify someone's C who wrote mainly in Fortran. It was basically Fortran with C syntax. You can write Fortran in any language.
|
|
|
|
|
I still do that. I tend to write Fortran in C# and JavaScript. 
|
|
|
|
|
I'm not aware of an arithmetic IF in C
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
