- then, have a viewer that parses both a log, and the source code for each logged line. Then, it can match a certain logged message with the actual line of C++ code. It can then interpret it.
Or it can integrate with the IDE. There is a lot more potential hiding under the encoding issue. Seamless navigation to source code line
As a side-note, right now you can log into the IDE, in case that IDE is for Windows - see destination::dbg_window()
is a simple example. A form of this is already achievable with your current library (I believe), just route the debug messages to the MS IDE and format the file+line information as that environment expects.
Yes ;)
Highlight the debug message and a function key will then put you on the spot. I'd assume that others have already wired that together.
Actually just pressing Enter on a line is enough :)
I have recently been through the third iteration of a significant logging development. One of the biggest things to emerge was the value of a standard encoding. Another was the difficulty of selling the idea ;-)
By standard encoding - do you mean how information is formatted, before being outputted, or this : http://en.wikipedia.org/wiki/Character_encoding ? Best, John -- http://John.Torjo.com -- C++ expert http://blog.torjo.com ... call me only if you want things done right