Re: Major problem with wide vs. normal strings in log messages

2008-05-23 Thread Dale King
On Fri, May 23, 2008 at 12:35 PM, Jacob L. Anawalt <[EMAIL PROTECTED]> wrote: > Dale King wrote: >> >> On Thu, May 22, 2008 at 7:55 PM, Jacob L. Anawalt >> <[EMAIL PROTECTED]> wrote: >>> >>> I get the same error if I write a wide >>> string to std::cout via <<. >> >> Not exactly. For std::cout all

Re: Major problem with wide vs. normal strings in log messages

2008-05-23 Thread Jacob L. Anawalt
Dale King wrote: On Thu, May 22, 2008 at 7:55 PM, Jacob L. Anawalt <[EMAIL PROTECTED]> wrote: I get the same error if I write a wide string to std::cout via <<. Not exactly. For std::cout all of the wide strings would print out as the address, not just some of them. Right, all uses of std::

Re: Major problem with wide vs. normal strings in log messages

2008-05-23 Thread Dale King
On Thu, May 22, 2008 at 10:37 PM, Curt Arnold <[EMAIL PROTECTED]> wrote: > > On May 22, 2008, at 6:21 PM, Dale King wrote: > >> Consider these statements on a platform (i.e. Windows) where WCHAR is >> used with various combinations of wide and normal strings: >> >> LOG4CXX_TRACE( logger, L"1" <<

Re: Server side socket usage

2008-05-23 Thread Ruud Bos
> The classes that emulate Java library classes are only there to support > log4cxx. They are not intended to be used a general purpose portable > runtime, that is the role for Apache Portable Runtime (APR). If you do use > them as a general purpose runtime, you need to be aware that any issues >