Well, you have a point there, but it's a little annoying to copy logging code into each module. (and there's no way I'm going to teach users how to use a debugger :P ) -rabidcow On Fri, 26 Jul 2002 13:47:35 EDT Bgvinyard@xxxxxxx writes: > In a message dated 7/26/2002 1:40:14 PM Eastern Daylight Time, > rabidcow@xxxxxxxx writes: > > > I've found it quite useful. I'm not sure I like the exact > implimentation > > but it's good enough. > > > > To the end user, logging is pretty much useless, but with logging > in the > > release build, you can ask them to send you a log. (and be sure > that the > > bug won't go away because of optimization differences) > > > > -rabidcow > > I was referring to the implementation specifically... and if a user > is having > problems then you send them a debug build, or a release build > compiled with > the OutputDebugStrings still compiled in and a debugger. Very few > debugging > messages should be left in a true release build. > > Message > > __________________________________________________ > Subscription options and archive: > http://www.freelists.org/list/shell-coding > > ________________________________________________________________ GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/web/. __________________________________________________ Subscription options and archive: http://www.freelists.org/list/shell-coding