{"id":55,"date":"2008-01-03T18:25:44","date_gmt":"2008-01-03T23:25:44","guid":{"rendered":"http:\/\/blogs.cae.tntech.edu\/mwr\/python-for-fortran-programmers\/"},"modified":"2008-01-03T18:25:44","modified_gmt":"2008-01-03T23:25:44","slug":"python-for-fortran-programmers","status":"publish","type":"page","link":"https:\/\/sites.tntech.edu\/renfro\/python-for-fortran-programmers\/","title":{"rendered":"Python for Fortran Programmers"},"content":{"rendered":"

I don’t know what language engineers will use in the future, but I know they’ll call it Fortran.<\/p><\/blockquote>\n

(Source unknown, some references here<\/a>.)<\/p>\n

Here’s a collection of Python translations of program listings from D.M. Etter’s Structured FORTRAN 77 for Engineers and Scientists<\/i>, 3rd Ed. Why this book? Because it’s what I used in my first (and only) Fortran class. To avoid potential copyright problems, I’m not including the original Fortran code, even though this might qualify as fair use. Spend the $1.00 plus shipping at AbeBooks<\/a>, or find it in your local used bookstore or library.<\/p>\n

I don’t claim that any of the following translations are good examples of idiomatic Python; when someone pointed out where some of my earlier code could be done much cleaner with functional programming techniques, I remarked “I’m less of a functional programmer than a dysfunctional one”. As I get time, I may go back and rework some of these in a more Pythonic manner.<\/p>\n