To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4cxx-ant has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4cxx-ant-static has an issue affecting its community
integration.
Thi
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4cxx-ant-no_wchar_t has an issue affecting its community
integration.
Currently, one cannot directly output a std::string through a logstream.
Rainer Schuetze and I both came up with the suggestion of calling .c_str() in
an operator<< function, but neither of us felt satisfied with this answer.
http://marc.theaimsgroup.com/?l=log4cxx-user&m=112229621903500&w=2
htt
Author: carnold
Date: Wed Apr 26 12:18:49 2006
New Revision: 397276
URL: http://svn.apache.org/viewcvs?rev=397276&view=rev
Log:
Bug LOGCXX-125: Broken multiple inclusion guard, header check workaround
Modified:
logging/log4cxx/trunk/include/log4cxx/helpers/bytearrayinputstream.h
Modified: lo
Steck, David wrote:
[...]
> On another topic, http://issues.apache.org/jira/browse/LOGCXX-82 looks like
> maybe it should be closed?
I fixed this some time ago, but AFAIR we left it open
because of some additional issues with the logstream class.
Since the issue which was reported with LOGCXX-82 i
