The only difference between WRITE_MODE and APPEND_MODE occurs when the stream is opened, except for this operation both modes are identical. WRITE_MODE and APPEND_MODE has nothing to do with the stream writing operation, both are sequential access to a stream. The difference is at opening operation; WRITE_MODE create a new empty stream and APPEND_MODE try to open and existing one. So, the next access write into a new stream or write into a existing one. Keeping the stream open both modes have the same "append" behavior. So, when simulation start, I like an empty transcription window or file; thinking the transcription windows and files as views of the stream model; WRITE_MODE do exactly that. Regards, saludos Walter El 2013-01-23 07:01, Martin.J Thompson escribió: >> -----Original Message----- >> From: owner-vhdl-200x@eda.org [mailto:owner-vhdl-200x@eda.org] On >> Behalf Of Brent Hayhoe >> Sent: 22 January 2013 23:48 >> To: vhdl-200x@eda.org >> Subject: Re: [vhdl-200x] RFC: std.textio.OUTPUT ? >> >> >> Whilst I agree that the current implementation is what users want and >> that we are not aiming to change that, it is important that the LRM >> reflect the reality. >> > [MJT] > Agreed > >> Both "STD_OUTPUT" and "STD_INPUT" are special kinds of I/O in that they >> are a shared resource and have all kinds of accesses before the actual >> simulated code 'run' actually opens the resource for its own use. > [MJT] > > Maybe that's the difference - I *perceive* the operation differently :) > > My mental model is of the transcript window displaying the "all kinds of accesses" *in addition* to a "tee" of a stream which carries the content of STD_OUTPUT. > >> >> As such, regardless of how this task is implemented within the >> simulator, any output to "STD_OUTPUT" will appear in the transcript as >> text appended to the existing output. >> >> I fail to see how this is anything but "APPEND_MODE". >> > [MJT] > I agree, the transcript does operate in append mode. My only difference is that I don't model the transcript window as *the* STD_OUTPUT, just one view on it, along with "other things". And my mental model is also independent of simulator implementation - it's just my model :) It may be my mental model is in "error"? > > However, I'm not one to get "all het up about it" - I can adjust my mental model to the transcript window "being the stream"... In which case, if the simulator creates a logfile (as well as the transcript display), should that be a new one per simulation restart, or a continuously appended one? > > Cheers, > Martin > -- ----------------------------------------------------------- Walter Daniel Gallegos Programmable Logic & Software Consultoría, Diseño, Entrenamiento. Montevideo, Uruguay EMAIL waltergallegos@adinet.com.uy Tel +598 26 23 44 60 | Cel +598 99 18 58 88 ----------------------------------------------------------- El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Jan 23 04:21:57 2013
This archive was generated by hypermail 2.1.8 : Wed Jan 23 2013 - 04:22:38 PST