#include "common.h"
#include <stdio.h>
#include "machine.h"
#include "plot3.h"
Include dependency graph for fortran.c:
Go to the source code of this file.
Defines | |
| #define | F(lc, uc) lc |
Functions | |
| void | pl_strncpy (register char *out, register char *in, register int sz) |
| void | F (ifdopn, IFDOPN) |
| void | F (ifopen, IFOPEN) |
| void | F (i2pnt, I2PNT) |
| void | F (i2line, I2LINE) |
| void | F (ilinmd, ILINMD) |
| void | F (i2move, I2MOVE) |
| void | F (i2cont, I2CONT) |
| void | F (i2labl, I2LABL) |
| void | F (i2spac, I2SPAC) |
| void | F (ierase, IERASE) |
| void | F (i2circ, I2CIRC) |
| void | F (i2arc, I2ARC) |
| void | F (i2box, I2BOX) |
| void | F (icolor, ICOLOR) |
| void | F (iflush, IFLUSH) |
| void | F (i3spac, I3SPAC) |
| void | F (i3pnt, I3PNT) |
| void | F (i3move, I3MOVE) |
| void | F (i3cont, I3CONT) |
| void | F (i3line, I3LINE) |
| void | F (i3box, I3BOX) |
| void | F (f2pnt, F2PNT) |
| void | F (f2line, F2LINE) |
| void | F (f2move, F2MOVE) |
| void | F (f2cont, F2CONT) |
| void | F (f2spac, F2SPAC) |
| void | F (f2circ, F2CIRC) |
| void | F (f2arc, F2ARC) |
| void | F (f2box, F2BOX) |
| void | F (a2spac, A3SPAC) |
| void | F (f3spac, F3SPAC) |
| void | F (a3pnt, A3PNT) |
| void | F (f3pnt, F3PNT) |
| void | F (a3move, A3MOVE) |
| void | F (f3move, F3MOVE) |
| void | F (a3cont, A3CONT) |
| void | F (f3cont, F3CONT) |
| void | F (a3line, A3LINE) |
| void | F (f3line, F3LINE) |
| void | F (a3box, A3BOX) |
| void | F (f3box, F3BOX) |
A FORTRAN-callable interface to libplot3, which is a public-domain UNIX plot library, for 2-D and 3-D plotting in 16-bit signed integer spaces, and in floating point.
Note that all routines which expect floating point parameters currently expect them to be of type "float" (single precision) so that all FORTRAN constants can be written normally, rather than having to insist on FORTRAN "double precision" parameters. This is at odds with the C routines and the meta-file format, which both operate in "C double" precision.
Note that on machines like the Cray, (C float == C double == FORTRAN REAL) != FORTRAN DOUBLE PRECISION
Also note that on the Cray, the only interface provision required is that the subroutine name be in all upper case. Other systems may have different requirements, such as adding a leading underscore. It is not clear how to handle this in a general way.
Note that due to the 6-character name space required to be generally useful in the FORTRAN environment, the names have been shortened. At the same time, a consistency of naming has been implemented; the first character or two giving a clue as to the purpose of the subroutine:
Definition in file fortran.c.
1.4.6