Backwards compatibility in different programming languages

Again, no problems with it. There is no call to delete any such support from compilers whatsoever.

I urge everyone to think about, “For whom Fortran, for what

Does Fortran aspires to be a big tent of many different users?

Or is it simply meant to be used by a select few in big $$ taxpayer-funded institutions who keep running “old codes” and a few hobbyist or single/small team coders who will easily cater and crater to “power” and say “I don’t mind implicit none” and daftly go about typing it everywhere and not care about others who don’t want to be that way any longer, at least in year 2032, noting the practitioners like mindless minions have been inserting implicit none in all their units since the late 1970s and wondering when they can stop with this nonsense.

With the teams I am working with where there is the potential of large, large teams developing many big, big simulation applications and also tools around their workflows involving literally trillions of dollars of infrastructure investment toward the transformation of energy industry away from fossil fuels. The coders and managers simply don’t want to see, hear, or write implicit none anymore, ok? With such massive investments at stake, a basic consideration is type safety in the new code being developed. And there is no single way besides the standard to go about this in Fortran: it’s one thing with Intel Fortran, another with AMD, a third with GCC, a fourth with NAG Fortran, etc… More importantly though, the coders want to arrive at ISO-certified workflows with ISO standard code at play i.e., Fortran standard code where they will not be required to insert implicit none all over the place. No one has the time to give a damn about the 1950s and IBM and implicit typing and FORTRAN history, ok?

Why cannot the needs of these new users be met by the Fortran standard? Why in the hell are some people always bringing up so much resistance at a possible change more than a decade from now that does not affect them any, it has no affect on existing codes, and it simply standardizes what everyone is doing now anyway? This only matters because the needs of practitioners is effectively dictated by a silly plebiscite-like scheme, a lot of “up” votes, or at least few to “no” down votes. The resistance and incessant opposing comments lead to lack of support because the compiler vendors only see current paying customers, they entirely fail to the potential of new customers and thus, they resist change.

Is it extreme bias and discrimination as to for whom Fortran is supposed to be and for what purposes? Is it being a soupn$@!, the ultimate parody of extreme bias and discrimination in current times where it shall depend on who is asking for something and how, otherwise it is “no soup for you” angry retort in the world of Fortran?

Why are some people so attached to variable names starting with i thru’ n to be integers by default when they can achieve the same by inserting just one line themselves rather than forcing everyone else who doesn’t want that to insert a line everywhere to disable that?

5 Likes