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

On May 22, 2008, at 6:21 PM, Dale King wrote: I'm going to file a bug on what I consider a major problem with wide versus normal character strings and the << operator to append to the MessageBuffer. The problem is that the first thing in your message determines the behavior of the rest of the m

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

On Thu, May 22, 2008 at 7:55 PM, Jacob L. Anawalt <[EMAIL PROTECTED]> wrote: > Dale King wrote: >> >> Most of the << operators in the MessageBuffer class return either >> CharMessageBuffer & or std::ostream &. I think all of these should >> probably be returning MessageBuffer which would allow it t

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

Dale King wrote: Most of the << operators in the MessageBuffer class return either CharMessageBuffer & or std::ostream &. I think all of these should probably be returning MessageBuffer which would allow it to switch to a WideMessageBuffer if I ever add a wide string, not just if the first string

Major problem with wide vs. normal strings in log messages

I'm going to file a bug on what I consider a major problem with wide versus normal character strings and the << operator to append to the MessageBuffer. The problem is that the first thing in your message determines the behavior of the rest of the message. If the first thing you output is not a wid

error building log4cxx 0.10.0 on hp-ux

Hi All, I am getting error when run "make command" for building log4cxx-0.10.0 on HP-UX B.11.11 U 9000/785 as shown below: Making all in cpp source='action.cpp' object='action.lo' libtool=yes \ DEPDIR=.deps depmode=none /bin/sh ../../../depcomp \ /bin/sh ../../../