🚀 go-pugleaf

In article <7120@pt.cs.cmu.edu> epperly@osnome.che.wisc.edu (Tom Epperly) writes:
>The following short fortran program gives a
>Fatal error in: /usr/lib/fcom1.31 Segmentation fault
>Nice error message!  I really don't know fortran, so I am not sure if this
>is a bug in the compiler or not.  Line seven is the line which causes the
>compiler to die(the one with the MOD).
>
>	PROGRAM test
>	IMPLICIT none
>	INTEGER level, igr
>	igr = 1
>	level = 2
>	igr = MOD(level,INT(10.0))
>	END
>

We ran into a similar situation on the 3100.  The problem is probably
caused by the use of INT inside the MOD function.  According to DEC, 
the MIPS Fortran compiler doesn't support (at least on the 3100) type
conversion of a CONSTANT (variables work okay) within a function call,
using the intrinsic conversion functions. 

You can use:  
   igr = MOD (level,10)

or you can use:
   itemp=INT(10.0)
   igr = MOD(level,itemp)

or you can use:
   igr = MOD(level,INTUSE(10.0))
   (where INTUSE is a user-defined conversion function (which could just 
   call the INT function))

or you can use:
   temp=10.0
   igr = MOD(level,INT(temp))

>Lastly, I am posting this for one of the users on our system; and I don't know
>why he wrote the MOD that way.

I'm not sure why anyone would want to do that either, but we tripped over the
same thing, so your user's programming style isn't entirely unique :-), even
though it may not be good programming practice.