- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
I would like to know if it is possible to disable the 'implicit open' feature of CVF and IVF languages. I explain; when doing I/O operations on unopened files, the runtime library automatically createsa file named 'fort.n' (n being the logical unit to be accessed and I don't want to use the FORTn environment variable because n can take many values). I would prefer to get an error message instead of this behavior. Is it possible ? (my goal is to build a dll in which I don't want to have problems with Vista in case of the file to be accessed has been disconnected for any reason and when I am not sure where the implicit file will be created).
Thanks.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'd think that a simple check (using INQUIRE) when your DLL first wants to access the unit should be sufficient. Once the first I/O is done, the unit won't become disconnected without being closed first.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you steve,
This is what I was thinking but I wanted to be sure. My main concern is about how to manage I/O operations to a file that has been (for any reason) disconnect by a unwanted close.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page