Simply fortran 2.11 serial3/29/2023 ![]() Paul, Please keep this feature in your list. One of these days we could investigate using column numbers when reporting errors but there are many more useful things to do first. I won't go into the details but it is not simply a matter of dealing with tabs. The FTN95 error report seems reasonable to me. But may be FTN95 will ask you if you are going to lose a bit your freedom by rejecting all TABs in your source files in favor of spaces and for that as a bonus you will get direct fingering with an arrow on your potential error place ? The FTN95 does not care about tabs which i think is good though John Campbell may disagree. Src/io/diagnostics.F90(603): warning #5112: Extension to FORTRAN-90: tab formatting Here is an example from Intel Fortran when i inserted a tab before WRITE: Intel and gFortran are doing this because they also have the warning if you are using TABs in source code instead of spaces. I understand that there will be a difficulty to implement this nice direct fingering on a wrong place. For such users definitely just showing on the wrong place is the most valuable hint. Words in all cases are so different and are in general right but the novice will break his mind deciphering them. *** Only INTEGER constants are allowed as a KIND parameter Īnd gFortran fingers not with the arrow but with the number 1 below Code:Įrror: Parameter 'i4' at (1) has not been declared or is a variable, which does not reduce to a constant expressionĠ002) integer(i4) :: iCurrHDFconvertorVersion (note i commented out the definition of i4) then Intel gives the following report Code:Īaa.f90(2): error #6683: A kind type parameter must be a compile-time constant. !! INTEGER, PARAMETER :: i4 = SELECTED_INT_KIND(9) It will be almost impossible to me to reproduce this error as there is no Linux FTN95 and manually compiling in BATCH file hundreds of files i still not succeeded to do. That compilation took place inside one of modules of that huge PIC code we discussed last month. It would be nice if we could also provide the column number but FTN95 begins by removing all unnecessary white space which means that column numbers are not easily available. Maybe you are right about this particular error but in general FTN95 has a good reputation regarding the clarity of its error reporting.įTN95 provides the line number of the error but not the column number. ![]() You have not provided the code that produced this error report nor the corresponding FTN95 error report This way they will not be turned off from this compiler ![]() Most of people barely know Fortran terminology and even English. Src/io/diagnostics.F90(254): error #6405: The same named entity from different modules and/or program units cannot be referenced. Is it possible to implement this with FTN95 ? Not only they describe the error, they also explicitly show it. This is what i like about gfortran and Intel with their method of explaining the compilation errors. Posted: Tue 10:55 pm Post subject: Visual compilation error diagnostics Profile Log in to check your private messages Log in :: View topic - Visual compilation error diagnosticsįAQ Search Memberlist Usergroups Register
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |