| Summary: | f77 man page needs updated | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Randall Hopper <aa8vb> |
| Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | CC: | aa8vb |
| Priority: | Normal | ||
| Version: | 3.4-RELEASE | ||
| Hardware: | Any | ||
| OS: | Any | ||
State Changed From-To: open->closed There's no f77(1) man page on -current, it's a link to g77(1). g77(1) in turn doesn't display the quoted paragraph. I also couldn't find that paragraph in the info docs. Please contact the GNU folks if this is still an issue. |
f77(1) says "From the user side of view this FORTRAN to C translation is completely transparent - f77 looks like a traditional FORTRAN compiler." However, pop this in a file: SUBROUTINE XMDF2T(APARM) IMPLICIT DOUBLE PRECISION(A) INTEGER INT1 DATA FR/0D0/ INTEGER INT2 99998 END and compile using "f77 -c tst.f": Error on line 5 of tst.f: Statement order error: declaration after DATA f77 compilers will eat this, but f2c will not. This is briefly mentioned in f2c.ps. Fix: Please update man page with caveats of use resulting from using f2c over a FORTRAN compiler. Thanks. Note: f77 and f2c from ports generates the same behavior, so the f77 port man page should probably be updated as well. How-To-Repeat: See above. This is causing me major grief trying to cook a FreeBSD port for the FeatFlow CFD package (www.featflow.de). I realize f2c isn't under our control. Therefore the man page should at least be updated with caveats.