Ritzert@DMZRZU71.BITNET (03/09/90)
I will start porting f2c as soon as my gcc1.37 is complete (which will take 1-2 weeks due to the speed of bitftp). f2c converts Fortran code to its C equivalent. Its based on the "real" *nix f77. Compiling the resulting c-code with pcc-based c-compilers leads to nearly identical executables as the f77-compiled original. f2c is free software. Michael
dav@eleazar.dartmouth.edu (William David Haas) (03/11/90)
In article <900309083947.691399@DMZRZU71-UNI-MAINZ--GERMANY>Ritzert@DMZRZU71.BITNET writes: >I will start porting f2c as soon as my gcc1.37 is complete (which will >take 1-2 weeks due to the speed of bitftp). f2c converts Fortran code to >its C equivalent. Its based on the "real" *nix f77. Compiling the >resulting c-code with pcc-based c-compilers leads to nearly identical >executables as the f77-compiled original. f2c is free software. > >Michael Don't count on it. We have some *BAD* FORTRAN code here that f2c fails on. If the FORTRAN is nice and clean it may work without any problems. Expect to hack the converted code to make it work. -dav
Ritzert@DMZRZU71.BITNET (03/18/90)
> (William David Haas) > > Don't count on it. We have some *BAD* FORTRAN code here that f2c fails on. > If the FORTRAN is nice and clean it may work without any problems. > Expect to hack the converted code to make it work. > -dav Thanks for the remark, I will be careful using f2c. Meanwhile I brought it up. It required mainly a bit of hacking file names, thanks to the decent gcc system. To test it, I built an Erlgraph metafile interpreter with it (on our unix box) and it worked. The Erlgraph (commercial graphics system) code is not very efficient but rather clean ... It will be posted soon. Michael mjr@dmzrzu71.bitnet