Greg Hudson wrote:
>On Mon, 2004-05-17 at 22:34, Branko Čibej wrote:
>
>
>>Yes... I can't reproduce it either. It's horrible, really :-( In my
>>experience, logging to a file is the best way to find these bugs.
>>
>>
>
>Why do people say such nice things about Windows development tools when
>they can't seem to help with the most basic of debugging tasks?
>
>
Which people? :-)
>>I don't think it would be very hard to reproduce syslog behavious on
>>Windows. Actually, I'd be against reinventing the wheel here, and just
>>use log4c (http://log4c.sourceforge.net/). I think it can use syslog on
>>Unix automagically.
>>
>>
>
>Appears to require gcc, and not work on Windows currently. And really,
>logging isn't a big enough problem to justify a new library dependency.
>Adding a bit of code to APR (perhaps ripped from the still-bleeding
>heart of httpd's server/log.c) seems like the optimal solution.
>
>
Oh, I suppose so. I suggested log4c because I'm very happy with log4j,
and log4c seems to be a straight port. The GCC dependency and not
running on Windows shouldn't be hard to fix.
>>>and partly because I have no idea how to locate a global
>>>configuration file under Windows.
>>>
>>>
>>Of course we do.
>>
>>
>
>I said *I* didn't. I didn't say *we* didn't. :)
>
>
Ah! Semantic details. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 18 05:04:49 2004