Databases
StackOverflow2013
Postsdbo
POWriting and calling pure subroutines in Fortran 90 using gfortran
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWriting and calling pure subroutines in Fortran 90 using gfortran
    primarykey
    data
    text
    <p>When writing and calling pure subroutines in Fortran 90 using gfortran, how do I find out why the compiler emits this error?</p> <pre><code>Error: Subroutine call to XXXX at (1) is not PURE </code></pre> <p>I'll try to pose my question as specifically as I can while at the same time being general enough to be useful to others, so I'll avoid pasting in my actual code and instead will sketch what happened.</p> <p>I understand there are various rules about pure procedures in Fortran 90, which I think basically boil down to not permitting side-effects in either functions or subroutines, and not permitting changes to subroutine parameters declared with <code>intent(in)</code>. I've a series of subroutines which initially were not declared to be pure, and whose parameters didn't have declared intent, but which nevertheless didn't perform side-effects. First, I changed all parameter declarations to have explicitly-declared intent, either <code>in</code>, <code>out</code>, or <code>inout</code>. Then, I declared all the subroutines to be <code>PURE</code>. Naturally, many errors occurred on the first attempt, but the compiler told me what the errors were (such-and-such parameter with <code>intent(in)</code> is being modified, for example), so one-by-one I fixed them all. </p> <p>There are calls among these procedures, however, and so now I still get many errors of the form shown above: <code>Subroutine call to XXXX at (1) is not PURE</code>. What I don't understand is <em>why</em> the call is not pure. I've done everything I can think of to make XXXX pure, but the compiler still thinks it isn't.</p> <p>So my question --rephrased-- is: how do I get gfortran to tell me WHY it thinks XXXX is not pure?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USire_and_curses
    1. USDavid A. Ventimiglia
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWriting and calling pure subroutines in Fortran 90 using gfortran
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWriting and calling pure subroutines in Fortran 90 using gfortran
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMaybe you could post your code, and then we'll work backwards to a generic answer?
      singulars
      1. POWriting and calling pure subroutines in Fortran 90 using gfortran
      1. USF'x
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload