There was the $SHORT compiler directive that made FORTRAN/66
programs compatible with FORTRAN/77.

Then there was the $ANSI compiler directive that flagged
warnings on HP extensions that didn't meen ANSI standards.

There is (was?) an $HP3000_16 direcive with parameters of
[ OFF | ON | ALIGNMENT | REALS | STRING_MOVE ]

The options were mutually exclusive and had a disclaimer that
said "Do not use the HP3000_16 compiler directive if the application
that is ported from MPE V to MPE/iX is not affected by any of the
above incompatibilities, ..."

Options were:

STRING_MOVE - Emulates a ripple move [which is used in MPE V (and
skid row)] for overlapping character substrings.

REALS - Emulates MPE V floating point data.

ALIGNMENT - EMULATES MPE V data alignment.

ON - Turns on all three options (ALIGNMENT, REALS and STRING_MOVE)

OFF - Turns off all three options (ALIGNMENT, REALS and STRING_MOVE)

Tracy Johnson
MSI Schaevitz Sensors


-----Original Message-----
From: Tom Emerson [mailto:[log in to unmask]]
Sent: Friday, June 29, 2001 2:23 PM
To: [log in to unmask]
Subject: Re: Fortran66 & 77 HELP (long)


On Fri, 29 Jun 2001 14:00:11 -0400, Don Harrington
<[log in to unmask]> wrote:

>Gang;
>
>From Mr. Abootorab's message below and from examining our system here, I
>have gleaned the following:
>
>FTN - CM compiler
[...]
>FTNXL, FTNXLGO, FTNXLLK - NM compiler command files
>
>My sitiuation is:
>
>We have a number of source files that appear to be FORTRAN 66.  It is
>suggested, below, that we convert from 66/V to 77/V before going NM.  My
>question then is this: What program do I use to compile those 77/V
>programs, or am SOL?

From MPE's help file:

:HELP FTN

FTN

     Compiles a Compatibility Mode HP FORTRAN 77/V program. HP
     FORTRAN 77/V is not part of the 900 Series HP 3000 Computer
     System Fundamental Operating Software and must be purchased
     separately.  The Native Mode equivalent of this command is
     FTNXL.

[...]

so the CM compiler FTN.PUB.SYS is the one you would want.  Theoretically,
you couldn't even compile a fortran 66 program, but I suspect there is a
compile time switch ($-directive?) that informs the compiler that the
source is really fortran-66 and should be treated accordingly (either that,
or there is a parameter/option of the actual FTN command to indicate this,
but a quick perusal of the help file didn't seem to show any such parameter)

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *