forums.silverfrost.com

[mecej4]

I created a small test program to check what FTN95 does when a formatted read is attempted using E10.2 as the format when the input field does not contain a decimal point, and the file being read has been opened with BLANK = 'ZERO'.

[PaulLaidler]

mecej4

Thank you for the feedback. I will make a note that this needs investigating.

[LitusSaxonicum]

There's a list of IOSTAT values and their meanings in the FTN77 manual. Are they the same in FTN95? IOMSG looks useful - is there a list of those too?

Eddie

[JohnCampbell]

Is the problem that IOSTAT = 0 ? ie the error was not detected ?

[PaulLaidler]

Eddie

The following code runs successfully using either FTN77 or FTN95...

[LitusSaxonicum]

Hi Paul,

That's a useful facility, but they are, after all, Fortran error messages, not IO error messages. I was a bit confused by the 451*, as the sensible messages do stop at 447.

I paraphrased mecej4 and JC's demos down to this (in old-style):

[PaulLaidler]

Eddie

451 is the upper limit for FTN95 whilst 447 is for FTN77.

The IOstat value is the index in the list of FTN95/FTN77 runtime errors.

[LitusSaxonicum]

Paul,

I got hieroglyphics when I upped the limit to 451 in your demo.

Eddie

[PaulLaidler]

Eddie

The upper limit for FTN95 relates to the latest version of the DLLs.

[mecej4]

Paul's program above, modified to reach up to n = 451, gives "hieroglyphics" for n = 448 to 451 when compiled for 32 bit. With /64, the messages are:

[LitusSaxonicum]

Ah! That explains it.

Still doesn't tell me where to look for the documentation though.

Eddie

[mecej4]

In the FTN95 help file (ftn95.chm), look for the title "Execution errors and IOSTAT values". That will take you to a list of 447 error messages. There are four more newly added messages that are yet to make their way into the CHM file.

The online help at https://silverfrost.com/ftn95-help/asm/error_messages.aspx appears to have become corrupted. The title says "Error Messages", but the subtitles have to do with assembler, CODE..EDOC, etc.

[PaulLaidler]

Eddie

You and mecej4 are right. The list for 32 bit FTN95 is not up to date.

It turns out to relate to a part of the FTN95 build process that I was unaware of. Either that or I had totally forgotten it.

The list is in ftn95.chm under Program development->Run time diagnostics->Excecution errors and IOSTAT values.

[LitusSaxonicum]

Got it, thanks.

Then I do think that the entry under 'Execution errors and IOSTAT values ought to be complemented by a line that says that the text from the table corresponding to a particular IOSTAT returned value can be retrieved with IOMSG=

I always shied away from IOSTAT because the return values are different for every compiler, although settling for FTN95 'until death do us part' makes that less of a consideration nowadays.

A disadvantage of running with a licensed version as against the PE is that the costs of upgrading militate against acquiring every single version update, and although some files and DLLs are provided for download, they don't include the CHM helpfile. It is also the case that many of the updates and bug fixes are in parts of the compiler that I probably never use, which is a factor in not updating every version as well as a Shylockian parsimony on my part.

Thanks both for the enlightenments.

Eddie

[PaulLaidler]

The original failure reported by mecej4 on this thread has now been fixed for the next release of the DLLs.

A range error for the exponent was not being trapped. The new IOSTAT value is 452 and the corresponding message is "Exponent out of range on read".