V
valtih1978
A file declaration opens a file implicitly when file open information is
included. Specification does not say when file is closed.
included. Specification does not say when file is closed.
A file declaration opens a file implicitly when file open information is
included. Specification does not say when file is closed.
And, I can close the implicitly opened file at any time?
KJ said:When compiling with VHDL '93, there won't be any implicitly opened files.
The files won't be open until you explicitly open them.
Still, they can be opened during elaboration (the old fashioned way) if
declared as follows:
file fh: text open write_mode is "my_file.txt";
I guess this could be called "explicitly opening the file".
No. FILE_OPEN(f) is explicit when user calls it manually! The
declaration-specified open information calls this function implicitly. I
just wonder when the corresponding FILE_CLOSE(f) is or can be called in
this case?
Alan Fitch said:All I can find in 1076-2002 is
"If a file object F is associated with an external file, procedure
FILE_CLOSE terminates access to the external file associated with F and
closes the external file. If F is not associated with an external file,
then FILE_CLOSE has no effect. In either case, the file object is no
longer open after a call to FILE_CLOSE that associates the file object
with the formal parameter F.
An implicit call to FILE_CLOSE exists in a subprogram body for every
file object declared in the corresponding subprogram declarative part.
Each such call associates a unique file object with the formal
parameter F and is called whenever the corresponding subprogram
completes its execution."
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.