Silverfrost Forums

Welcome to our forums

use_virtual_scratch_files@ available for ftn95?

12 Feb 2019 4:15 #23237

Hello,

in Salford's ftn77 environment there was a call to enable or disable the virtual scratch file facility, namely

use_virtual_scratch_files@ 

. If the virtual scratch file facility was enabled, files opened with STATUS='SCRATCH' were never written to disk but held in virtual memory.

Now, I could not find use_virtual_scratch_files@ in Salford's ftn95 compile environment.

Hence I would like to know, if the virtual scratch file facility is available under ftn95, and if so, by which call I would enable or disable it.

Thanks, Dietmar

17 Feb 2019 5:30 #23254

I can't find any reference to scratch files that are 'virtual'.

There are routines for mapping files to memory such as MAP_FILE_FOR_READ_WRITE@ but I have not looked up the details.

18 Feb 2019 11:11 #23255

Paul,

It's in the FTN77 library manual, available on this website. If it never migrated from FTN77 to FTN95, and given that it seems so sensible, isn't there a case for resurrecting it?

Eddie

20 Feb 2019 2:23 #23266

As most disk I/O is now buffered, why worry about virtual files; disk files would probably give similar performance.

Please login to reply.