Re: declaring a file local to a sub-procedure

Do you understand the difference between a static and a dynamic variable?
Both can be in subprocedures.

Now, FTM:
"What's new in this release" subsection "Files defined in subprocedures":
Files can be defined locally in subprocedures. I/O to local files can only
be done with data structures; I and O specifications are not allowed in
subprocedures, and the compiler does not generate I and O specifications
for externally described files. By default, the storage associated with
local files is automatic; the file is closed when the subprocedure
returns. The STATIC keyword can be used to indicate that the storage
associated with the file is static, so that all invocations of the
subprocedure will use the same file, and if the file is open when the
subprocedure returns, it will remain open for the next call to the
subprocedure.

There was some discussion on the list before whether it's better to do
something like
D FileOpen s 1n inz(*off) static
/free
If not FileOpen;
Open TheFile;
FileOpen= *on;
setll...;
EndIf;
...

Some people like using a work variable instead of if %Open(...). Something
to do with less overhead and whatnot.

Rob Berendt