![]() Progress logging is a case in which that happened, and I rewrote the routine shortly after the publication of that article, 5 years ago. ![]() That robust implementation almost always becomes part of a write-and-forget-about-it DLL. Where our viewpoints may differ is that I may start with that dead-simple use case, but, more often than not, I find new uses that break it, and the simple implementation that met the original use case gives way to a very robust implementation that can handle just about anything that you throw at it. ![]() With all that said, on the whole, I agree with you. Though most run in visible console windows, I've had a fair number of them that were destined to run in hidden consoles, mostly belonging to the SYSTEM account.īear in mind, too, that my use case involved strings of text, which got very messy when they found their way into a redirected stream file. I've written hundreds of console-mode programs, in VBScript, Perl, Python, C, C++, C#, and even assembler. Progress messages are incidental, and usually meaningless in that context. ![]() When a console program runs as part of a scheduled task in a different user context (such as the SYSTEM account), it must be able to save anything critical that gets written to STDERR. I had a very specific use case in mind in which capturing STDERR is important. It's not often that you see a Code Project article that doesn't need a supporting download. The simplicity of your approach is the reason I gave your article 5 stars.
0 Comments
Leave a Reply. |