forums.silverfrost.com

[PaulLaidler]

JohnCampbell

/TABS is missing from ftn95.chm and I have corrected this.

[DanRRight]

So where is the good installation files for gfortran?

You get again these

*** Unwritable expresssions in read statement or
*** READ can have a maximum of two non-keyword specifiers

and you are guessing and guessing trying and trying different things to understand what the heck this may mean. Need second opinion from different compiler because that not user-friendly diagnostics got on my nerves. As if it was hard to tell that it is not allowed to over-write the parameter iz or what and where these freaking keywords specifiers are. What, there was competition to write things the shortest and most cryptic way as there are no memory to fit the compiler into 64kB floppy disk?

[JohnCampbell]

Dan,

Not sure what your post is asking, but yes, gFortran does have a better error message in this case:

FTN95 gives:
C:\temp\forum\dan\dan2.F90(8) : error 304 - Non-writable expression in READ statement
C:\temp\forum\dan\dan2.F90(8) : error 52 - Compilation abandoned

gFortran gives:
C:\temp\forum\dan\dan2.f90(8) : error - Named constant 'iz' in variable definition context (item in READ) at column 1
Compilation failed.

iz is a parameter so can't appear in a read statement.

I am in the good position of having FTN95 and gFortran installed and can easily switch between them in PLATO Ver 5, switching via
Tools > Settings > Miscellaneous

Regarding installing gFortran, there are a number of options for downloading, and I have an approach via environment variables to make installs of both gFortran and FTN95 easier to manage. I'm sure I have explained this in previous posts.

[DanRRight]

Thanks John. What specifically installation do you have? Please provide the exact link. There are many different options i do not have time to try

[JohnCampbell]

Dan,

equation.com > Programming tools > Fortran, C, C++
This provides a self extracting file, eg gcc-8.3.0-64.exe
download and then install into : C:\Program Files (x86)\gcc_eq\gcc_8.3.0

Then create the following environment variables, either via a .bat file or via control panel > system
(these work on Win 7)

set f95.ver=8.40F
set _gcc.ver=8.3.0

set _gcc_dir=C:\Program Files (x86)\gcc_eq\gcc_%_gcc.ver%
set gcc_path=%_gcc_dir%\bin;%_gcc_dir%\libexec\gcc\x86_64-w64-mingw32\%_gcc.ver%
set EQ_LIBRARY_PATH=%_gcc_dir%\x86_64-w64-mingw32\lib

set gcc.ver=%_gcc.ver%
set gcc_dir=%_gcc_dir%

set f95_dir=C:\Program Files (x86)\Silverfrost\ftn95_%f95.ver%
set ftn95_path=%f95_dir%
set f95include=%f95_dir%\include
set mod_path=%f95_dir%\include

set Path=C:\ProgramData\Oracle\Java\javapath;%gcc_path%;%ftn95_path%;%orig_path%;c:\utils

Note:
1) set orig_path= " this is the original path prior to installing gFortran or FTN95, but excluding some unnecessary rubbish. your call !
I create orig_path in Control Panel > System > Advanced system settings > Environment Variables > System Variables > New... by cutting and pasting of Path value.
2) all other variables can be created similarly. I have chosen names as their sorted order is important. MS Win 7 does not do multiple pass definition !!
3) changing installed versions is merely changing the value of f95.ver and _gcc.ver to the appropriate value.
4) c:\utils contains most of my own programs to help with programming.

5) equation.com version of gFortran is different to mingw-w64 version (used for clearwin64 ?) in that it is a static build that does not use .dll's. I find this satisfactory.
If you need to use clearwin64, ie gFortran + clearwin+ graphics, that requires .dll's, you may need to install mingw-w64 version. Downloading is a bit more complex, to choose the options you require. I have both but would need to review my last install ( forgotten the options !! )
6) Typically FTN95 is my preferred software development and when combined with /IMPLICIT_NONE is my most reliable approach.

[DanRRight]

OMG...i need to chose among something again.

Question to SF: is it true Clearwin+ does not work with Equation dot com version ?

Meantime here is another code demonstrating unclear, cryptic, elitist or wrong diagnostics of FTN95 input/output. User-made error of not setting "filename" as character variable is identified wrong way or hell knows what the message says. FTN95 is very good at fining errors. But what it burbs in its South / Texas accent often simply impossible to decipher

[mecej4]

In this case, I think that the compiler did a fine job. It gave you the line number, and even the clause of the statement on that line that it found to be incorrect.

We could have expected the compiler to complain about the preceding line first, since that line (Line-1) is also in error, since a character expression is being assigned to a real (by implicit naming rules F... is real) variable. Indeed, you may try commenting out the second line of the source code and running the compiler on it again.

I have a suggestion for you. You can get the FTN95 compiler to give you error numbers by using the option /ERR . You can then prepare a text file, say, errlist.txt, with error messages worded as you please, in a language of your choice (North Texan, South Polar, etc.), indexed by the error number. If you type the Windows command

findstr <nnnn> errlist.txt

where nnnn is the error number given by the compiler, you can see your wording of the corresponding message.

[DanRRight]

hahaha Really drunk logic from both of you, FTN95 + mecesj4. Even not two bugs are here but three: not only FTN95 missed the bug on first line, or reported crazy message on second, it mixed out the order by reporting second line error which was caused by error in the first line.

I'd change each and every error messages if was not translating every english word.

[JohnCampbell]

Line 1 is not an errror, but could be compatibility with ftn 4 storing characters in a real variable.

[DanRRight]

John, looks like not super-duper compatibility too . The filename is 4 bytes, 'zzzOut.data' is 3 times more.

[mecej4]

[mecej4]

--DUPLICATE POST, Please Delete---

[JohnCampbell]

It may be an error in the Standard, but isn't it a common extension supported for backward compatibility ?

[mecej4]

If the variable were of type INTEGER, perhaps, but assigning a character constant to a REAL variable would almost guarantee incompatibility, since no mainframes that I know of had IEEE reals, and on PCs we have had IEEE compatibility from the time that the first IBM PC arrived. What the Apple II did, I do not know -- possibly, software emulation on the 6502, which did not have FP instructions.

[JohnCampbell]

I didn't have to look very far. CDC Fortran certainly allowed it, as did Pr1me.
The following is taken from a Pr1me implementation in 1980's.
FTN77 on Pr1me was my first experience of Salford Fortran.

The following was compiled with Pr1me FTN.
I think FTN77 also supported this.
Lines 2 and 3 were my changes for CDC > Pr1me