Comix wrote: > On Fri, Feb 20, 2009 at 3:02 PM, Sebastian Moors <[email protected]> wrote: > >> Hi, >> >> has anyone an explanation why it is useful to use a seperate thread for >> logging? Ok, we can safe messages in a queue and write them to a file >> easily ( no need to reopen the file often). But the queue seems to be >> not really useful for debugging, sometimes it's confusing because you >> can't see the output of INFOLOG or something in the terminal because it >> segfaulted before the logger thread got active, but the program flow >> reached a line or two *after* the output. No a big problem when you do >> step-by-step debugging with a compiler, but it can confuse you >> sometimes. And the logfile, well, i haven't used this feature or saw >> anyone using it. >> > > You cannot write to stdout inside the realtime thread, that's the > reason why I wrote the separate thread. > The logger class can be modified to write directly to stdout in debug > mode, just use the --verbose flag to activate this behaviour. > The log file is useful when people starts Hydrogen without a console > (e.g: macosx, windows). > > Ciao > > Hi,
thanks to both of you!! That was a very good explanation! Sorry for not seeing this in the first time :( Its quite obvious that realtime threads can't handle the output be themself.. - Sebastian ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Hydrogen-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
