As already answered, you need to specify widths. Something like ES14.5 might work well for the floating point format. There is a short cut for the integer format: I0 will cause the compiler to use the number of digits needed.
It is call action(mySubX) provided action looks as subroutine action(sub) !either – not recommmended, it is old FORTRAN77 style external sub !or – recommended interface subroutine sub(aA, aB) integer,intent(…) :: aA, aB end subroutine end interface ! NOT BOTH!! call sub(argA, argB) provided action knows what to put there as argA, argB to represent aA, … Read more
One possible solution has already been presented to you which uses a “dummy variable”, but I just wanted to add that you don’t even need a dummy variable, just a blank read statement before entering the loop is enough: open(18, file=”m3dv.dat”) read(18,*) do … The other answers are correct but this can improve conciseness and … Read more
intent(inout) and intent(out) are certainly not the same. You have noted why, although you don’t draw the correct conclusion. On entering the subroutine useless a is undefined, rather than defined. Having a variable “undefined” means that you cannot rely on a specific behaviour when you reference it. You observed that the variable a had a … Read more
One method: read the line into a string, using a string that is at least as long as the longest expected line. Then you go about parsing the string. E.g., if the numbers are always split by spaces, use that to figure out the substring boundaries. Then you can use “internal reads” to read from … Read more
When compiling with ifort before version 17.0.1, the default behaviour is for the compiler not to use the Fortran rules for automatic allocation on intrinsic assignment. You will need to use an option like -assume realloc-lhs.
With RESULT(FluxArray), fluxArray is the name of the result variable. As such, your attempt to declare the characteristics in the result clause are mis-placed. Instead, the result variable should be specified within the function body: function Flux(W1,W2) result(fluxArray) double precision, dimension(3), intent(in)::W1, W2 double precision, dimension(3) :: fluxArray ! Note, no intent for result. end … Read more
You have some lengths 12 in the constructor, so it may be better to use length 12. Also, use instead character(len=12), dimension(5) :: models = [character(len=12) :: “feddes.swp”, & “jarvis89.swp”, “jarvis10.swp”, “pem.swp”, “van.swp”] Possibly even better, if you have compiler support, is character(len=*), dimension(*) :: …
What you care about here is association: you want to be able to associate entities in the function f with those in the subroutine condat. Storage association is one way to do this, which is what the common block is doing. There are other forms of association which can be useful. These are use association … Read more
There is no built-in “big number” support, but we can first check whether there is a larger integer kind available (as mentioned by Francescalus above and also many previous pages (e.g. this page). On my computer with gfortran-6.1, the compiler seems to support 128-bit integer kind, so I could calculate the result up to n=160 … Read more