forums.silverfrost.com

Yes, I meant in the fopen sense.
Regarding using fileinfo@ it would be possible in theory, but haven't tested if it fails for open files.

It fails also when accessing via unit number
INQUIRE(UNIT=iunit, EXIST=fexists, SIZE=fsize, IOSTAT=ios)

Also FILE_SIZE@ and FILE_SIZE8@ seem to fail with files that are already open , so they cannot be used unless we close the file in question file first.

As per code below, Ftn95doesn't support the SIZE keyword in INQUIRE statements. This is quite important I think.

PROGRAM TEST_INQUIRE_SIZE
IMPLICIT NONE
INTEGER :: fsize, ios
...

Confirmed fixed!

Would it be possible to have updated EXE/DLLs in the support page? Thanks

This is my Windows version
OS Name: Microsoft Windows 11 Home
OS Version: 10.0.26100 N/A Build 26100

Whenever I try to compile the following subroutine (32bit or 64bit, v9.12.0), I am getting

subroutine test_regression ()
REAL, ALLOCATABLE :: AIN(:)

nk = 1 ...

if I use SDBG to visualise the contents of a variable that contains greek characters from a utf-8 file they look garbled up. If I put print statements that go to a cmd console window I can see them pr ...

HI, I presume this is not fixed yet? Thanks

We have an issue where a corrupt file causes an array to be populated with UNDEFINED via READ routines (as per other topic https://forums.silverfrost.com/viewtopic.php?t=4825&highlight=undefined) ...

Is this included in iso_c_binding?
https://gcc.gnu.org/onlinedocs/gfortran/C_005fASSOCIATED.html
It is quite important because it checks the validity of C style pointers

I am building a DLL file with a series of object files (.o in Gfortran or .obj in Silverfrost). I cannot put the same object more than once as it will complain that a function is already defined.

Thanks for the reply, but I don't quite understand. Are you saying that you are building a .LIB file first?
I was saying that with SLINK64 (or SLINK) I never have any issues with undefined reference ...

Is FTN95 the only linker where the order of the object files is not important? It seems that in Gfortran if they are not put in the correct dependency order, then it will throw up undefined reference ...