Are you running it in VC in debug mode? (you have to do Debug-Start from the IDE- then View Menu- Other Windows- Output- you might have to scroll it) Too bad we don't have a boost.socket, because it would be fairly reasonable to take and make a sink for debug out, on windows it would use OutputDebugString- or on windows \ unix\ it could spit debug info to a socket). If we had a Socket library, all the rest of the pieces are there... I am going farther down the profiling path, (and Christopher Diggins has been INCREDIABLY helpful there). But as I think about it- boost isn't really that far off from having a profiler\debugger\logger. I think the iostreams lib would be an excellent thing to build that on top of... Anyways, just mindless meandering.. Ill give the code below a run tonight and see if it works for me (3-4 hours from now).
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Jonathan Turkanis Sent: Monday, February 28, 2005 5:11 PM To: boost@lists.boost.org Subject: [boost] Re: Re: Iostreams Question: Best way tooutputtowin32debugger\outwindow ?
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.
Jonathan
struct debug_out_sink : boost::iostreams::sink { debug_out_sink () { using namespace boost::iostreams; chain_.push(newline_filter(newline::windows)); chain_.push(debug_out_sink_impl()); }
void write(const char* s, std::streamsize n) { chain_.write(s, n); }
boost::iostreams::detail::chain<boost::iostreams::output> chain_; };
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost