https://gunkies.org/index.php?action=history&feed=atom&title=32v_1m_rc 2026-05-06T03:55:22Z Revision history for this page on the wiki MediaWiki 1.30.1 https://gunkies.org/w/index.php?title=32v_1m_rc&diff=7014&oldid=prev 2009-10-26T15:28:58Z

<p>New page: RC(1) UNIX Programmer&#039;s Manual RC(1) == NAME == rc - Ratfor compiler == SYNOPSIS == rc [ option ] [ file ] ... == DESCRIPTION == _R_c invok...</p> <p><b>New page</b></p><div>RC(1) UNIX Programmer's Manual RC(1)<br /> <br /> <br /> <br /> == NAME ==<br /> rc - Ratfor compiler<br /> <br /> == SYNOPSIS ==<br /> rc [ option ] [ file ] ...<br /> <br /> == DESCRIPTION ==<br /> _R_c invokes the Ratfor preprocessor on a set of Ratfor source<br /> files. It accepts three types of arguments:<br /> <br /> Arguments whose names end with `.r' are taken to be Ratfor<br /> source programs; they are preprocessed into Fortran and com-<br /> piled. Each subroutine or function `name' is placed on a<br /> separate file _n_a_m_e._f, and its object code is left on _n_a_m_e._o.<br /> The main routine is on _M_A_I_N._f and _M_A_I_N._o; block data subpro-<br /> grams go on _B_L_O_C_K_D_A_T_A?._f and _B_L_O_C_K_D_A_T_A?._o. The files<br /> resulting from a `.r' file are loaded into a single object<br /> file _f_i_l_e._o, and the intermediate object and Fortran files<br /> are removed.<br /> <br /> The following flags are interpreted by _r_c. See _l_d and _f_c(1)<br /> for other flags.<br /> <br /> -c Suppresses the loading phase of the compilation, as<br /> does any error in anything.<br /> <br /> -f Save Fortran intermediate files. This is primarily<br /> for debugging.<br /> <br /> -r Ratfor only; don't try to compile the Fortran. This<br /> implies -f and -c.<br /> <br /> -v Don't list intermediate file names while compiling.<br /> <br /> -C Preserve comments in output, and format esthetically<br /> (indentation, mostly).<br /> <br /> -6x Place continuation character in column 6, instead of<br /> non-standard convention used by _f_c(1).<br /> <br /> Arguments whose names end with `.f' are taken to be Fortran<br /> source programs; they are compiled in the normal manner.<br /> (Only one Fortran routine is allowed in a `.f' file.)<br /> <br /> Other arguments are taken to be either loader flag argu-<br /> ments, or Fortran-compatible object programs, typically pro-<br /> duced by an earlier _r_c run, or perhaps libraries of<br /> Fortran-compatible routines. These programs, together with<br /> the results of any compilations specified, are loaded to<br /> produce an executable program with name a.out.<br /> <br /> == FILES ==<br /> ratjunk temporary<br /> /usr/fort/fc1 Fortran compiler<br /> <br /> == SEE ALSO ==<br /> B. W. Kernighan, _R_A_T_F_O_R - _A _p_r_e_p_r_o_c_e_s_s_o_r _f_o_r _a _R_a_t_i_o_n_a_l _F_o_r_-<br /> _t_r_a_n, Bell Laboratories CSTR #55, 1977.<br /> [[32v 1m fc|fc(1)]] for Fortran flags and error messages<br /> [[32v 1m ld|ld(1)]] for loader flags<br /> [[32v 1m f77|f77(1)]] for the latest Fortran<br /> <br /> == DIAGNOSTICS ==<br /> Yes, both from _r_c itself and from Fortran.<br /> <br /> == BUGS ==<br /> #define and #include lines in `.f' files are not processed.<br /> fc(1) is unsupported.<br /> <br /> [[Category:32v man section 1]]</div>

Neozeed