[patch #4570] win32 NSLog debugger output

[Richard Frith-Macdonald]

Update of patch #4570 (project gnustep):

                  Status:                    None => Need Info              
             Assigned to:                    None => CaS                    

    _______________________________________________________

Follow-up Comment #1:

I'm not familiar with windows ... I changed the code to make debugger output
and event logging conditional on the 'syslog' setting as I was told that the
previous behavior was causing problems for people and that this stuff on
windows was pretty much analagous to syslog on unix.

However, having lookad at this patch I'm no longer sure that the debugger
output and the event logger should be considered together ... perhaps I
misunderstood the complaints due to my unfamiliarity with windows.

So ... can you please confirm for me that the function to produce output to
the debugger has no unwelcome side effects ... ie it does not have a huge
impact on performance when a lot of NSLog() output is produced (that is to
say, comparable performance impact to writing to stderr is ok, but a worse
performance impact is probably not), and it does not produce an effect on the
system that will frighten/confuse end users.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?func=detailitem&item_id=4570>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/