Return to printed_doc CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / new / help / src / f77

Annotation of 43BSDTahoe/new/help/src/f77/printed_doc, revision 1.1.1.1

1.1       root        1: .TI F77/PRINTED_DOC "Sep. 4, 1985"
                      2: Printed Documentation
                      3: .de Xp
                      4: .in \\n(RIu
                      5: .ti -\\n(RIu
                      6: ..
                      7: 
                      8: The following documents may be purchased at the Computing Services
                      9: library, 218 Evans Hall, U.C. Berkeley, Berkeley, California 94720, 
                     10: (415) 642-5205.  New users should start with "Communicating with UNIX",
                     11: "Edit: a Tutorial" and then "A Guide for VAX UNIX Fortran Users".
                     12: 
                     13: .Xp
                     14: "Communicating with UNIX", Nov. 1984, Ricki Blau, Jane Wolff,
                     15: UNX 1.3.1, 22 pages.
                     16: An introduction to UNIX for new users.  Designed to
                     17: be used with "Edit: a Tutorial".
                     18: 
                     19: .Xp
                     20: "Edit: a Tutorial", Sept. 1984, Ricki Blau, James Joyce, Jane Wolff,
                     21: UNX 3.3.1, 30 pages.  An introduction to the UNIX editor, 'edit', for new
                     22: users.
                     23: 
                     24: .Xp
                     25: "A Guide for VAX UNIX Fortran Users", March 1985, Jerry Berkman,
                     26: UNX 2.3.3, 70 pages.  This assembles in one place
                     27: a variety of information relevant to f77 use that is otherwise
                     28: scattered throughout the UNIX documentation.  It includes many
                     29: example programs, and explains how best to write, maintain, and
                     30: debug Fortran programs on UNIX.
                     31: It also includes the material in the f77 help files.
                     32: Although some of the information is specific to UC Berkeley,
                     33: most of the information is of general interest.
                     34: 
                     35: .Xp
                     36: "An Introduction to the C shell", Nov. 1980, William Joy, UNX 1.3.10,
                     37: 46 pages.  An extensive discussion of the C shell command
                     38: interpreter.  This covers more advanced material than
                     39: "Communicating with UNIX".
                     40: 
                     41: .Xp
                     42: "A Portable Fortran 77 Compiler", Sept. 1985,  S. I. Feldman and
                     43: P. J. Weinberger, UNX 2.2.10, 25 pages.  This is a reference
                     44: document that describes f77 by listing the differences between
                     45: the language it compiles and the 1977 and 1966 Fortran standards.
                     46: It is a terse document, not intended for beginners.
                     47: 
                     48: .Xp
                     49: "Make - A Program for Maintaining Computer Programs", Aug 1978, S. I. Feldman,
                     50: UNX 11.2.2, 9 pages.  This reference for the 'make' program
                     51: maintenance system is written for C programmer's. As a Fortran
                     52: programmer, you are better off starting with "help f77 make"
                     53: and "help f77 style" or with the description of 'make' in
                     54: "A Guide for VAX UNIX Fortran Users".
                     55: 
                     56: .Xp
                     57: "Introduction to the f77 I/O Library", Sept., 1985, David L. Wasley, 11 pages.
                     58: This is a technical description of the f77 I/O library.
                     59: 
                     60: .LP
                     61: All except for "Communicating ..." and "A Guide ..." are
                     62: part of Vol. 2C of the "VAX UNIX Programmer's Manual".

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.