forums.silverfrost.com

[mike.smartcam]

Thank you for the advise and assistance from all
_________________
Regards

Mike

[JohnCampbell]

As Mecej4 has stated : "There are no separate rules for what you can have or not have in include-files."

There is a lot of flexibility in what you place in an include file.
I have used an include file list (all.f90), being include "filex.f90" to simplify the compile and link procedure. It makes the command much simpler, by effectively having only one file for the whole project. Finally: "FTN95 all /link" builds the project.
I use this approach to enable argument list checking or group those routines that I want to include for a /timing option. ( I'd recommend everyone should review the /timing option, as it is very useful for checking performance. Just make sure you exclude some of the low level routines.)

To think of the resulting file, after all includes have been merged gives a good understanding. Include can be any group of Fortran code snippets that suit the purpose.

John

[LitusSaxonicum]

MECEJ4,

When you port code from one compiler to another, you invariably run foul of the extensions allowed by the original compiler, and disallowed by the second. If you allow yourself to be distracted by altering your programming style at this point, you will compound the problem of ever getting the program working with the new compiler.

Watcom's authors took a different line on extensions to the standard than the authors of FTN77, the latter choosing to provide extra system routines (usually, but not always of the SUBPROGRAM@ variety). Watcom, on the other hand, permits extensions to Fortran 77 that look more like later Fortrans.

It's a moot point as to whether the facilities of Fortran 90/95/2003 are always of much benefit to the engineer who programs (as distinct to a computer scientist steeped in conventional theory), especially in the case of the former who just wants his DOS or mainframe software to work on his PC in Windows so that he can go on using it

If I was starting from scratch, and I were decades younger, then I would probably follow your advice to the letter. In this case, and at this point in the process, it may well not be the most helpful suggestion.

Eddie

[mecej4]

Eddie, the OP wrote "At this stage I am just trying to build working modules prior to porting to a Windows application." That is why I suggested using modules instead of common blocks.

It is reasonable to expect that the OP is going to evaluate any suggestions given here as to suitability, time commitment, usefulness, etc., before adopting them. If OpenWatcom were a viable replacement for the defunct Watcom compiler, and he/she is aware of OpenWatcom, there would have been fewer reasons to consider switching compilers. Given that a switch is being made, there is an opportunity here to make some worthwhile improvements.

[LitusSaxonicum]

Understood, and point taken. However, don't forget that 'module' meant 'separately compilable file' for long before it meant what it does in Fortran 90 et seq.

E

[mecej4]

About "load modules", a la IBM 360. It took me many months to digest that concept, given that the only interface allowed ordinary mortals involved turning in a pack of punched cards and coming back a day later to receive the cards with printed output.

I think that even today some large computers use "module" in the sense of a large system package, such as Abaqus or CERN, that the user's program is supposed to be linked to. There are shell commands to access and use such system modules.

[JohnCampbell]

Eddie,

You wrote

[Masoud.Ravan]

Hi group
I want to have a subroutine that could process on matrices...I have written a simple program but the compilation was failed and i got this error:
(((error 215 - Invalid expression on left hand side of assignment)))
Program Code:
PROGRAM TEST
IMPLICIT NONE
INTEGER N
REAL, ALLOCATABLE :: A( : ), B( : )
READ(*,*) N
ALLOCATE(A(N))
ALLOCATE(B(N))
A=1
CALL TDMA(N, A, B)
END PROGRAM

!-----------------------------------

SUBROUTINE TDMA(N,A, B)
INTEGER I
DO I=1, N
A(I)=B(I)
END DO
END SUBROUTINE TDMA

Help me Please

-----
Regards
Masoud[/code]

[PaulLaidler]

In the subroutine you need to declare A and B as arrays. Since you are passing the size of the arrays, you could use this in the array declaration.

[JohnCampbell]

You need to declare A and B in the subroutine.
Also, as you have A = B, you also need to initialise B with values before you use it. The following applies these corrections.