Hello Danny, log4cxx is in a stabilization stage, so I won't include functionnal changes to existing classes. The log4j team has redesigned the PatternLayout syntax for log4j 1.3 The present version of log4cxx is based on log4j 1.2.8
Michael Selon Danny Pike <[EMAIL PROTECTED]>: > Michael, > > Oh. Is there any way that we can influence the log4j team or do I have to > go with a customized build? > > DP > > --On 05 July 2004 12:56 +0200 Michael CATANZARITI <[EMAIL PROTECTED]> wrote: > > > Hello Danny, > > > > The syntax of the PatternLayout directly comes from log4j. Excepted the > > date format, log4cxx can directly read a log4j configuration file. > > > > Michael > > > > Selon Danny Pike <[EMAIL PROTECTED]>: > > > >> I want to be able to put the process ID in my debug output, as well as > >> single-character versions of the levels (w, e, d etc instead of "WARN", > >> "ERROR", "DEBUG"). > >> > >> I have already modified my version of log4cxx to support these but it > >> would make me more comfortable if they could be added to the standard > >> build. In particular, what is the system (if any) that people are using > >> to choose the pattern token in the format string (%F, %L etc). The only > >> comment in the source that I can find appears to be incomplete. Is > >> there a standard way of deciding what these should be? > >> > >> I'm happy to make the code changes myself (as I've already done it on my > >> own copy), but they are scattered over several files in the source so > >> it's not just a case of uploading one or two whole files. > >> > >> Regards, > >> > >> DP > >> > >> > > > > > > > > >
