🚀 go-pugleaf

Does anyone have experience using FORTRAN on the NeXT?

We are using Absoft's implementation, which gives the possibility of
using the C preprocessor (cpp), thus allowing statements like #include
and #define to appear in your FORTRAN code.
We use header files to #define a set of constants, and use the same
header files in C- as well as FORTRAN programs. This is not only for
ease of maintenance, but also because cpp knows how to look in standard
directories for include files.
But cpp also removes comments, which it thinks start with /* or, on the
NeXT (in Objective C), with //.
But a double slash is used in FORTRAN for character array concatenation.
Running cpp with the option -C to tell it not to remove comments has
the unwanted effect of presenting the FORTRAN compiler with all
comments from the (C-style) header files.

Is there a way out of this, apart from not using // for concatenation?

--
Jan-Willem de Bruijn          ...!uunet!mcsun!sun4nl!dutrun!dutnak2!jwdb
Seismics and Acoustics                        jwdb@dutnak2.tn.tudelft.nl
Faculty of Applied Physics         Discipline is never an end in itself,
Delft University of Technology         only a means to an end.