RE: [vhdl-200x] RFC: std.textio.OUTPUT ?

I agree... regarding the transcript window.

However what is/should be the behaviour of any actual file logged (by the simulator) for the OUTPUT stream?  

Currently the simulators behave by logging to a file and then "tee"ing that file to the transcript window (or at least that's the behaviour I see as a user - what they actually do under the hood is immaterial as this point).  This is (I would think) the behaviour that users desire.  In addition, I would regard it as complying with the current standard in that the file written to is not appended.  The transcript window is a user-convenience which behaves in a useful way (that is not constrained by the LRM).

Cheers,
Martin



> -----Original Message-----
> From: owner-vhdl-200x@eda.org [mailto:owner-vhdl-200x@eda.org] On
> Behalf Of Jim Lewis
> Sent: 21 January 2013 17:55
> To: VHDL-200x
> Subject: [vhdl-200x] RFC: std.textio.OUTPUT ?
> 
> Hi,
> The definition of the file OUTPUT, does not seem consistent with its
> implementation.  std.textio defines OUTPUT as follows:
>    file OUTPUT: TEXT open WRITE_MODE is "STD_OUTPUT";
> 
> Based on the way it works it seems to be implemented as:
>    file OUTPUT: TEXT open APPEND_MODE is "STD_OUTPUT";
> 
> For WRITE_MODE, the LRM says:
>    If the value supplied to the Open_Kind parameter is WRITE_MODE,
>    the access mode of the file object is write-only. In addition,
>    the external file is made initially empty. Values written to
>    the file object are placed in the external file in the order
>    in which they are written.
> 
> For APPEND_MODE, the LRM says:
>    If the value supplied to the Open_Kind parameter is APPEND_MODE,
>    the access mode of the file object is write-only. In addition,
>    the file object is initialized so that values written to it
>    will be added to the end of the external file in the order in
>    which they are written.
> 
> 
> Based on this, when a simulator writes to the file OUTPUT, it should
> first empty the file/transcript window.  Its behavior is much closer to
> APPEND_MODE.
> 
> I think simulators are doing the correct action and suggest that this
> is resolved by changing the definition of the file OUTPUT to use
> APPEND_MODE.
> 
> Comments?  If others agree, then this needs to be entered as an ISAC
> issue.
> 
> Best,
> Jim
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Jim Lewis
> Director of Training             mailto:Jim@SynthWorks.com
> SynthWorks Design Inc.           http://www.SynthWorks.com
> 1-503-590-4787
> 
> Expert VHDL Training for Hardware Design and Verification
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
> 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.