Hi, I atempted to include the whole module in this reply (not my code, so I'm not comfortable cutting it down), but although I can see it in Preview, it disappears once the message is posted. I'm guessing a line limit, but I cannot find instructions on this, or on how to attach a file.
I have uploaded the responsible code to:

FTN95 reports two errors
"error 246 - The END statement cannot be used to end an internal SUBROUTINE, use END SUBROUTINE instead" (that's pretty clear, no problem about doing that).
and
"error 304 - Non-writable expression in READ statement"
applying to the first read. That's too cryptic for me. In the documentation I cannot find a list of errors and less cryptic meanings. Does such a one exist?

These errors are not picked up in Lahey fortran or Intel fortran (X64).

All help most gratefully received. I'd really like to be able to run this code.
Thank you for your time and help, I truly appreciate it.

The Salford/Silverfrost compiler does not know how to process subprogram dummy arguments with the allocatable attribute, which are not legal in Fortran 95 without the TR 15581 extensions.

Had you passed the allocatable arrays individually, instead of their being squirreled away within a derived type, the compiler would have given you an appropriate message. But, since 'wave_obj' has components that are allocatable, the compiler is confused.

Last edited by mecej4 on Tue Feb 22, 2011 11:56 am; edited 1 time in total

I didn't mean to be critical of defining and using structured variables. The error messages that a compiler emits can be incomprehensible when it has been given code in a language version that it does not know about, but the user expects it to be able to compile.

I thought I would never see this error, as I still write in Fortran 77 style, and thought it was a fancy modern sort of thing that was causing your message. However, I saw it yesterday. It came inside a loop where I was asking:

Code:

READ(27,*) (A(I), B(I), I=1,Number_of_Things)

First of all I checked Number_Of_Things was spelled correctly. Of course, the error was failing to dimension both A and B!

FTN95 error messages are usually very understandable. I had to puzzle out what this one meant, and that took longer than fixing the underlying problem. Mostly they tell you what is wrong in "Fortran programmer" language, so you can immediately tell what you have to do to fix it. The "Non-writable ..." etc message is telling you how the compiler sees it.