Curt Arnold wrote:
On May 10, 2005, at 1:06 PM, Kevin Tew wrote:
I'm getting tons of these warnings for every log4cxx class Any Ideas?
c:\Branches\main\cb\ExternalLibs\include\log4cxx\helpers \appenderattachableimpl.h(106) : warning C4250: 'log4cxx::helpers::AppenderAttachableImpl' : inherits 'log4cxx::helpers::ObjectImpl::log4cxx::helpers::ObjectImpl::addRef' v ia dominance
c:\Branches\main\cb\ExternalLibs\include\log4cxx\helpers \objectimpl.h(32) : see declaration of 'log4cxx::helpers::ObjectImpl::addRef'
Haven't seen these before, will review when I switch from log4j development, to APR, then to log4cxx development on Win32 in the next day or so. What version of Microsoft Visual C++ are you using?
VS.NET 2003
I saw the body for void RollingFileAppender::rollOver() was commented out.
I was also wondering about the state of the rollingfileappender?
I just updated to CVS head to get the NTEventLogger changes for local api access instead of RPC.
The RollingFileAppende use to work good enough for me. It it still functional or is it out of commision until you finish your work on it?
I've committed changes to fix some bugs in the log4j 1.3 RFA implementation that needed to be fixed before starting porting. There are still a few things that I want to fix there before bring the code over.
In a perfect world, unless you are writing an extension appender, layout or similar, you never work with a LogString. However, it is likely that there are some places where std::string and std::wstring methods should be added.
log4cxx/helpers/transcoder.h provides macros to convert from the external string types
to the internal string type. However, use of those in client code should be rare.
This was the method that I was having trouble with?
This may already be on your todo list.
RollingFileAppender(const LayoutPtr& layout, const LogString& fileName, bool append);
Kevin Tew
