projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| c1030a02 TL |
1 | .TH RC 1 |
| 2 | .SH NAME | |
| 3 | rc \- Ratfor compiler | |
| 4 | .SH SYNOPSIS | |
| 5 | .B rc | |
| 6 | [ option ] [ file ] ... | |
| 7 | .SH DESCRIPTION | |
| 8 | .I Rc | |
| 9 | invokes the Ratfor preprocessor on a set of Ratfor source files. | |
| 10 | It accepts three types of arguments: | |
| 11 | .PP | |
| 12 | Arguments whose names end with `.r' are taken to be | |
| 13 | Ratfor source programs; they are | |
| 14 | preprocessed into Fortran and compiled. | |
| 15 | Each subroutine or function `name' is placed on a separate file | |
| 16 | .I name.f, | |
| 17 | and its object code is left on | |
| 18 | .IR name.o . | |
| 19 | The main routine is on | |
| 20 | .I MAIN.f | |
| 21 | and | |
| 22 | .I MAIN.o; | |
| 23 | block data subprograms go on | |
| 24 | .I BLOCKDATA?.f | |
| 25 | and | |
| 26 | .IR BLOCKDATA?.o . | |
| 27 | The files resulting from a `.r' file are | |
| 28 | loaded into a single object file | |
| 29 | .I file.o, | |
| 30 | and the intermediate object and Fortran files are removed. | |
| 31 | .PP | |
| 32 | The following flags are interpreted by | |
| 33 | .IR rc . | |
| 34 | See | |
| 35 | .I ld | |
| 36 | and | |
| 37 | .IR fc (1) | |
| 38 | for other flags. | |
| 39 | .TP 6 | |
| 40 | .B \-c | |
| 41 | Suppresses the loading phase of the compilation, | |
| 42 | as does any error in anything. | |
| 43 | .TP 6 | |
| 44 | .B \-f | |
| 45 | Save Fortran intermediate files. | |
| 46 | This is primarily for debugging. | |
| 47 | .TP 6 | |
| 48 | .B \-r | |
| 49 | Ratfor only; don't try to compile the Fortran. | |
| 50 | This implies | |
| 51 | .B \-f | |
| 52 | and | |
| 53 | .B \-c. | |
| 54 | .TP 6 | |
| 55 | .B \-v | |
| 56 | Don't list intermediate file names while compiling. | |
| 57 | .TP 6 | |
| 58 | .B \-C | |
| 59 | Preserve comments in output, and format esthetically (indentation, mostly). | |
| 60 | .TP 6 | |
| 61 | .BR \-6 x | |
| 62 | Place continuation character | |
| 63 | .IT x | |
| 64 | in column 6, instead of non-standard convention used | |
| 65 | by | |
| 66 | .IR fc (1). | |
| 67 | .PP | |
| 68 | Arguments whose names end with `.f' are taken to be | |
| 69 | Fortran source programs; | |
| 70 | they are compiled in the normal manner. | |
| 71 | (Only one Fortran routine is allowed in a `.f' file.) | |
| 72 | .PP | |
| 73 | Other arguments | |
| 74 | are taken | |
| 75 | to be either loader flag arguments, or Fortran-compatible | |
| 76 | object programs, typically produced by an earlier | |
| 77 | .I rc | |
| 78 | run, | |
| 79 | or perhaps libraries of Fortran-compatible routines. | |
| 80 | These programs, together with the results of any | |
| 81 | compilations specified, are loaded | |
| 82 | to produce an executable program with name | |
| 83 | .BR a.out . | |
| 84 | .SH FILES | |
| 85 | ratjunk temporary | |
| 86 | .br | |
| 87 | /usr/fort/fc1 Fortran compiler | |
| 88 | .SH "SEE ALSO" | |
| 89 | B. W. Kernighan, | |
| 90 | .IR "RATFOR \- A preprocessor for a Rational Fortran" , | |
| 91 | Bell Laboratories CSTR #55, 1977. | |
| 92 | .br | |
| 93 | fc(1) for Fortran flags and error messages | |
| 94 | .br | |
| 95 | ld(1) for loader flags | |
| 96 | .br | |
| 97 | f77(1) for the latest Fortran | |
| 98 | .SH DIAGNOSTICS | |
| 99 | Yes, both from | |
| 100 | .I rc | |
| 101 | itself and from Fortran. | |
| 102 | .SH BUGS | |
| 103 | #define and #include lines in | |
| 104 | `.f' files are not processed. | |
| 105 | .br | |
| 106 | fc(1) is unsupported. |