On 22.05.12 21:44, Jon Elson wrote: > Matt Shaver wrote: > > > > I would also be interested in hearing from any people with experience > > in Fortran who would be interested in helping port this code to the > > Linux platform. If you could indicate your level of Fortran experience > > and any reasons for your interest in this code, that would be very > > helpful.
The minimum-effort "port" to linux might just be to shove it through gfortran, the fortran version of gcc, avoiding entirely the task of translating the source code to another language. As can be seen here: http://gcc.gnu.org/fortran/ Legacy code support right back to fortran77 might be a stretch, requiring some dusting of cobwebs off the APT code base. Although I haven't built gfortran, I see a lot of fortran testcases, and "info" documentation for fortran in the gcc sourcecode, which is encouraging. > Aughhhh! I used to write a LOT of code in FORTRAN, and I know "where > the bodies are buried". Ie. the kinds of things in FORTRAN that cause > endless trouble. The worst is having unmatching common blocks in > different parts of the code. Ahhh, I remember doing that as a student, while trying to expand my limited understanding of the documentation on common blocks. The uni lecturers were a fat lot of help once you went beyond the syllabus, to do anything unusual with the language. Mind you, that was back in 1973, so we didn't even have fortran77 then. > A compiler that permits something like the C include statement goes a > long way toward preventing those. There are a few more things that > either don't translate well or lead to other difficulties. Then gfortran might really be worth a close look, since it has moved forward since last century: »Compiler capability is quite extensive and includes nearly all g77 features. We highly encourage users to move from g77, which is no longer maintained, and start taking advantage of GFortran's modern features. Legacy g77 code will compile fine in almost all cases.« It does seem to compile the NIST F77 testsuite. And it seems to have supported "include" already prior to version 4.6, AFAICT: http://gcc.gnu.org/wiki/GFortran#GCC4.1 Coincidentally, I recently stumbled across the cardboard box of Hollerith punch cards which were submitted for batch processing of fortran programs back in '73, and returned with printout several hours later. By getting in before 9 a.m., I could get two runs per day! (Most students managed only one, and no others that I met learnt the mainframe's assembler language, which allowed me to hijack its peripherals, and lead the operator on a merry chase. ;-) Oddly enough, I never asked the lecturers for advice on that project. Erik -- Universities are places of knowledge. The freshmen each bring a little in with them, and the seniors take none away, so knowledge accumulates. - Harvard President A. L. Lowell ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
