NSLog and fprintf in base

[Wim Oudshoorn]

Error reporting to the user is done by 
calling either NSLog (..) or fprintf (stderr,...)
On Linux you can redirect NSLog to syslog.
However fprintf is not redirected to syslog.

I assume that fprintf is used when you want to
some error and the error can not safely be 
logged by NSLog () [NSLog uses locking and
base class functionality].

But wouldn't it be nicer if we replace
fprintf (stderr,...) with a custom 
log function that will also uses syslog?

Also at the same time we could use
the OutputDebugString methods on 
Windows as equivalent of the syslog on Unix.

Any reasons, why this change would not be good?

Wim Oudshoorn