JD,你好！ Almost every debugger could catch the message output by OutputDebugString(W) API in Windows box. ======= 2007-04-01 16:23:37 你在来信中写道：=======
Richard Day wrote:
I havent had a chance to look at your code or pantheios yet but I am interested in your library. A boost library would be something to standardize on for larger projects. One facility I like to have however is the ability to output to the debugger. Does yours do this or do you intend to add it ?
Output to the debugger? You mean pass some kind of message to the debugger? And what the debugger does with those messages, just print them? I didn't think about that actually. But I guess there is no standardized way to do this, it depends on the debugger you use, or worst your system. I'm not sure an eventual Boost.Logging library should deal with this, but at least let some space for a particular user to append a interface to the debugger easily. How can it be done and still retain the simplicity of the library?
Its not always feasible to do this for performance reasons though so you need to be able to toggle it off and on of course(Full screen games are my biggest culprit there). I have a very simple library I wrote myself to allow this but it is lacking some features as well. It seems everyone has their own homegrown solution to this.
I think this is why there is still no logging library integrated into boost. Everybody has his idea (and sometime his own library) and nobody is able to agree on the minimum specification and stick with it. That is why my proposal is to define a small set of specifications, the lowest common denominator. I'm reading the old threads on this subject and try to aggregate something.
JD
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
= = = = = = = = = = = = = = = = = = = = 致 礼！ missdeer missdeer@gmail.com 2007-04-01