Hi Andrew, That's pretty much what I had to do. Fortunately, I had already been using macros to do all of my logging, so I just changed my project's logging macros to adapt.
In your case, however, you're going to have to either cut and paste a lot of code, or re-factor a lot of code. ( Log4cxx dev team, please correct me if I'm wrong. ) Stephen Bartnikowski Barking Lizards Technology www.barkinglizards.com -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Chalk Sent: Tuesday, February 06, 2007 12:26 PM To: [email protected] Subject: Upgrading to v0.9.8 I had to upgrade an app. that used log4cxx. We made a lot of use of lines like: LOG4CXX_INFO(eventLogger, _T("Binding to: " << sBindIP.c_str() << ". Port: " << usPort << ". Link: " << sLinkNo.c_str())); I.e. we used inline ostringstream constructs. In 0.9.8 none of this appears to work. We appear to have to make major modifications to our code along the lines of: ostringstream os; os << _T("Binding to: " << sBindIP.c_str() << ". Port: " << usPort << ". Link: " << sLinkNo.c_str()); LOG4CXX_INFO(eventLogger, os.str().c_str()); Am I missing a way to continue with inline ostringstream? Many thanks.,
