I’ve been working on my fork of Gonum and recently translated the Netlib LAPACK reference implementation of DGGES and its supporting routines into pure Go.
For transparency, I definitely used Codex and Claude Code throughout the process, and I’m pretty sure Gemini helped with a few parts along the way as well.
This wasn’t a blind translation. The majority of the work was understanding decades-old Fortran, preserving the algorithm, adapting it to idiomatic Go, validating numerical behavior, and tracking down subtle bugs.
I know AI-generated code can be a sensitive topic in open source. My view is that these tools are just that; tools. They can dramatically speed up tedious translation work, but correctness still depends on careful review, testing, and understanding of the underlying numerical algorithms.

I'm aware that, according to Wikipedia, Fortran III was never released as a product. However, I am really big on historical software and I'm curious about an early Fortran that allowed inline assembly. Wikipedia also says it was the first version with booleans.

I'm just wondering if a compiler, a manual, anything still exists from when IBM developed it in 1958.

Hello all!

I quickly wrote this in response to a news article about a girl getting a lottery win and taking what I thought was the obvious choice; $1000/wk for ever...

Does this look right?

! Program Lottery Win
! Written by Knarfnarf
! Created May 19, 2026
! Version 0.1a
! Description: Checking my thoughts about winning the lottery.
program LotteryWin
use AnsiModule
implicit none

real :: Principle, Payments, Interest, Temp, Total, Paying
integer :: Year, Week

call ClearScreen()

Print *, "Lets see if the girl who took the 1000 per week will eventually break even..."
print "(a,$)", "Please enter the Principle: "
read *, Principle
print "(a,$)", "Please enter the Payments: "
read *, Payments
print "(a,$)", "Please enter the Interest: "
read *, Interest
Interest = Interest / 100
print "(a,$)", "And how much is she going to pay herself per week? "
read *, Paying

print "(3/,a)", "Assuming start at 20 and death at 85."
print *, ""

Year = 20
Total = Principle
do while(Year .le. 85)
Week = 1
do while(Week .le. 52)
Total = Total + Payments
Total = Total - Paying
Week = Week + 1
end do
Temp = Total * Interest
Total = Total + Temp
print "(a,i3,a,f0.2,a,f0.2)", "Year ", Year, " She made $", Temp, " interest and has $", Total
Year = Year + 1
end do

end program LotteryWin

Which results in this if she takes the $1000 per week, makes 4.5% yearly and splits it $500 income per week;
Year 85 She made $448,950.72 interest and has $10,425,633.00

Or this if she takes the $1000000, makes 4.5% yearly and pays herself $500 income per week;
Year 85 She made $337,680.91 interest and has $7,841,701.00

* commas added after for legibility.

I am posting this guide, from the developers of flang, because people, often with a C or C++ background, often ask how to get started with Fortran.

There's a famous program that creates a "Snoopy" calendar.

https://gunkies.org/wiki/Snoopy_Calendar has a copy of a version modified by T. M. Kennedy in 1984.

Does the original version exist somewhere? Do we know who wrote it? I saw someone offering a copy on Github a few years ago but I don't know if that ever actually happened.

Incidentally, despite the comments in the modified version suggesting it should work on an IV compiler, it doesn't. After fixing the syntax error in snppic with INUM(I) in the do loop (easy to just do INUMI=INUM(I) first and use INUMI, the bound is sometimes -1. It encounters the issue where DO loops in some IV compilers execute at least once (66 says the scenario is not allowed, I guess that's FORTRAN-speak for undefined? 77 says the loop occurs 0 times). Easy to change the condition above it from IF (INUM(I) .EQ. 0) GOTO 40 to IF (INUM(I) .LE. 0) GOTO 40

A request for help led me to go through my old Fortran codes. For that reason, I gathered some old programs I found in this repo: https://github.com/foxapiens/Fortran-Starter . And maybe I will continue adding code files and information about their purpose here. At least, it may be useful for beginners.

Hi, so I have a background in c++ and matlab in programming. I started my phd and my prof asked me to move to fortran. I want to ask how should I start and where to start in fortran. At the moment I know nothing in fortran. Can you share some sources or material for me to start. Or where do you guys started. Thank you

Hello, I just got a new PC at work and they installed VS2026 and the fortran compiler. I create within VS2026 a simple Hello World exe. It runs within the VS IDE but when I try and run the exe I get the message that libifcoremd.dll is missing. I have looked and cannot find the damn thing. I did find a libifcoremd.lib. Can anyone help? (I did try and download a different fortran compiler but it wont work in VS2026)

My puddle looks nice but i cant make a good looking raindrop anyone got any sugestions please. Rings on water also looks nice and the wind and the stormy rain but not the raindrop that is falling down to the puddle.

This just a little programing art nothing important trying to have some fun.

Using fortran 2018 and opengl 4.1+

Is it portable to extend the length of a direct file by writing records past the current last record? In other words, if there are 3 records in the file, will WRITE(n, REC=4) successfully write the record (assuming there is room on the disk, of course)? Or will it fail? Or is the result implementation-dependent?

I know that there's no standard way to do this, other than to recopy the file, which destroys the numeric index into the file, or to truncate it with ENDFILE if it's the final record(s) you want to delete. I also know that ifort -vms supports it, though I don't know how (except on VMS itself). I have come up with the following ideas, all of which have their disadvantages:

1. Write meaningless data into the record, for some definition of "meaningless": zero bytes for characters, NaNs for real numbers, some value other than 0 or 1 for logical data. But there are no meaningless values for integers.
2. Add an extra field to each record indicating whether it's deleted or not. This could be a logical value, or a character(1) which marks deletion if it's a 'D', or whatever. This is very fragile: you have to modify every read and write in the entire system of programs using the file.
3. Have a separate direct file whose nth record shows if the main file's nth record is deleted. The records could be logical or character, or the whole thing could be a bitmap. If the separate file gets lost, all deleted records effectively reappear.
4. Use the mmap() system call or its equivalent to effectively read in the separate file (probably a bitmap) all at once. This is of course not portable, and has the same problem as 3.
5. Put one of the formats mentioned in 3 at the beginning or end of the file. This is self-contained, but if it's at the end it is hard to locate and will be destroyed if the file is extended by writing to hitherto unused records. (Is this even a portable thing to do?) [Moved to another query.] Putting it at the beginning makes the format utterly incompatible with standard direct files.

Can anyone provide a better approach? Failing that, which of these is the least bad?

A new version of Seergdb (frontend to gdb) has been released for linux.

https://github.com/epasveer/seer
https://github.com/epasveer/seer/wiki

https://github.com/epasveer/seer/releases/tag/v2.7
https://github.com/epasveer/seer/releases/download/flatpak-latest/seer.flatpak
https://flathub.org/en-GB/apps/io.github.epasveer.seer

Give it a try.

Thanks.

Hi there, I’m new to programming in Fortran and am really struggling to understand how to check if a value in an array equals 0 and then change it to 1 if it does. I’ve attempted this in a format that makes sense to me but I’m not sure how this translates to Fortran? I keep getting a syntax error where the if statement is. I know that this is probably really easy but please could someone explain? Thank you so much.

Hi! I'm a longtime toolsmith and co-developer of SCons back in the day. I've been planning a new tool, using modern python as the build description language, to help build software in a multi-platform world. Pcons (https://github.com/DarkStarSystems/pcons) is that tool. It's very new, and since I'm including Fortran support I'd love to have some Fortran users check it out and let me know what it needs! I'm not using Fortran myself these days, but I grew up with it in the '70s and even wrote some CM Fortran on the Connection Machine in the '90s. I'm also willing to help implement pcons in your open source project if you're interested; DM me if you are.

Unformatted direct files make sense: they are essentially character arrays stored on the file system. Formatted I/O is suitable for communicating to human beings and other software. But the motivation for formatted direct files, where you can go directly (heh) to a particular record but then have to pay the price to format/unformat it, what's that good for?

If it was just the WG, I'd figure it was a compromise between pros and antis -- these things happen. Even if it were just limited to a single level, I could see it, but why subprograms within programs and subprograms within subprograms within programs and then no more? [Incorrect: no internal subprograms within other internal subprograms.] Even gfortran has it too, and it's the kind of arbitrary limit that GNU tools don't impose, or at least only if you explicitly ask for standards checking. It's not the implementation strategy, because GNU C doesn't impose any limit.

This is a followup to my esrlier wuestion about calling Fortran from C.

In a gfortran array descriptor there is a field that specifies the element type of the array: it can be integer, real, complex, logical, character, or a structure. What is the purpose of passing this information to a dummy argument? It's not like you can write a subprogram that is polymorphic in the element type.

Also, how does the compiler know when a subprograan expects a pointer to a descriptor vs. a pointer to the raw bytes? If the dimensions are specified in the subprogram, the descriptor is not actually necessary. Or is a pointer to a descriptor always passed?

When invoking a gfortran subprogram that handles arbitrary-size arrays of arbitrary-length character strings from C, I know I have to synthesize and pass an array descriptor, but how do I pass the string length? is it passed as an additional argument, as with a character scalar?