Fortran Wanted: Ancient Fortran FFT source code

AI Thread Summary
The discussion centers on a request for the source code of an early implementation of the Fast Fourier Transform (FFT) algorithm, specifically pre-Fortran77 code characterized by implicit typing, single-letter variable names, and a lack of comments. The original poster recalls encountering this code in the late 1990s while working for a large corporation and expresses surprise at its continued use despite its outdated and terse style. Respondents emphasize that the appearance of code is irrelevant to its functionality, noting historical practices such as the use of uppercase letters in the 1970s and the limitations of punched card programming, which discouraged more descriptive variable names. They also highlight that the mathematical nature of the FFT often leads to concise variable naming. A link to FFT-related resources is provided, although it does not directly address the request for the specific source code.
cdenzler
Messages
1
Reaction score
0
Hi.

I'm new here and wasn't sure which forum to post this request on, but this one seemed a good start.

I am developing a talk/seminar on dealing with legacy code. In the late 1990s I was working for a large corporation in a software capacity and one day idly wondered what the source code looked like that was actually performing the FFT in the application I was working on.

As near as I can recall, the code had the following features: Implicit typing, single letter variable names, source code in all caps, no commenting, and was very terse. I think I recall at the top of the file, the code was written by someone at UC Berkeley, but I could be wrong about that. I recall clearly that there was a date in the header comments, from the mid-1960s. It must have been an early implementation of the Cooley-Tukey algorithm.

At the time I was shocked that at the bottom of the call stack was this (then) 30-year old Fortran code that was doing an enormous amount of heavy lifting for this (very large) corporation. The code was ugly to look at, but there must have been a reason that it was still in use at the time.

I am looking for the source code, pre Fortran77, of this ugly gem if it rings any bells.

Thank for any pointers,

- Chris
 
Technology news on Phys.org
There is nothing very shocking about this. The compiler doesn't care if the code looks ugly, so long as it works.

Most high speed computer printers from the 1970s era only printed upper case letters.

Creating a deck of punched cards for program input, there were NO editing options whatever, except for throwing away a card and retyping the complete line. That didn't encourage using longVariableNamesWithRandomlyInsertedUpperAndLowerCaseCharacters.

In any case, the mathematical description of the FFT would have been written with one-character "variable names", just like almost every other piece of mathematics. Making the variable names longer when you translated the math into Fortran didn't add any value - in fact it was a good way to make mistakes.

"Real programmers" have better things to do than rewrite working code just to make it look pretty!
 
Dear Peeps I have posted a few questions about programing on this sectio of the PF forum. I want to ask you veterans how you folks learn program in assembly and about computer architecture for the x86 family. In addition to finish learning C, I am also reading the book From bits to Gates to C and Beyond. In the book, it uses the mini LC3 assembly language. I also have books on assembly programming and computer architecture. The few famous ones i have are Computer Organization and...
I have a quick questions. I am going through a book on C programming on my own. Afterwards, I plan to go through something call data structures and algorithms on my own also in C. I also need to learn C++, Matlab and for personal interest Haskell. For the two topic of data structures and algorithms, I understand there are standard ones across all programming languages. After learning it through C, what would be the biggest issue when trying to implement the same data...

Similar threads

Replies
1
Views
2K
Back
Top