Guten Tag Curt Arnold,
am Dienstag, 8. Juni 2010 um 05:08 schrieben Sie:
The hex codes were intentional since they would give the expected
character value even if compiled using a non-ASCII based encoding like EBCDIC.
Isn't this case already handled by the following in logstring.h?
#if
Guten Tag Thorsten Schöning,
am Montag, 31. Mai 2010 um 16:15 schrieben Sie:
[Linker Fehler] Unresolved external 'std::basic_stringchar,
std::char_traitschar, std::allocatorchar ::basic_stringchar,
std::char_traitschar, std::allocatorchar (int, int, const
std::allocatorchar)' referenced from
The hex codes were intentional since they would give the expected character
value even if compiled using a non-ASCII based encoding like EBCDIC.
I'll try to pull the constants out into preprocessor macros and do a little
#if(__BORLANDC__)
Hello,
I have to challenge the inclusion of Log4cxx in out projects based on
an old Borland Build 5 and 6. We already tried log4cpp but need the
SMTPAppender and rolling FileAppender which are not provided by
log4cpp as we need them.
I first tried the ant build of log4cpp but it doesn't seem to
