-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Jonathan Turkanis Sent: Monday, February 28, 2005 10:26 PM To: boost@lists.boost.org Subject: [boost] Re: Re: Re: Iostreams Question: Bestwaytooutputtowin32debugger\outwindow ?
Reid Sweatman wrote:
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Jonathan Turkanis
Okay Brian,
The following apparently works, but when OutputDebugString is called I don't see any output. I'm not sure if the previous version worked or not; I've run out of time for now.
I didn't see most of this thread, and may be totally off-base here, but you need to use a tool that can intercept the output from OutputDebugString(), as that function assumes there's a debugger attached to its process; if there's no attached debugger, it attempts to use the Windows system debugger, which must be both installed and active. However, I like SysInternals' DebugView, both because it's well-written and easy to use, and because it's free. Very lightweight alternative to invoking a full debugger when that would be overkill. It can do kernel-mode debugging, too, which is a major plus, if you need that; got a copy running on my other machine right now. www.sysinternals.com. And if this is not to the point, or you already know all this, bear in mind that I only had this post available, and skimmed it pretty cursorily, and please just disregard my post.
Thanks for the info.
The main point of the thread was to show how to write a sink with a built- in line-ending filter, so the user doesn't always have to add one explicitly.
Jonathan
[Brian Braatz Writes:] Yes. (sorry if I got off base)- the question relevant to boost \ iostreams was this- Given a device which has different line termination than \n, how do you handle it in such a way that allows for that device to be able to interpret std::endl so it works as the user would expect. (and so the code you write using the sink makes sense to the user) I happen to be using win32's outputdebugstring, but the same issue applies for "printing" to a windows edit control. The same issue might also apply to a daisy wheel printer. And, personally, I think boost should support daisy wheel printers (grin)....