log4cpp-devel — technical discussions about the development of log4cpp

[Log4cpp-devel] Warning: win32 dll can't export container classes

[David R. <dre...@mo...>]

I found this out when trying to use Category::getCurrentCategories(),
which returns std::set<Category*>*. The set I got had 1 good pointer;
the rest were invalid.

The problem is detailed by MS in Q168958 "HOWTO: Exporting STL
Components Inside & Outside of a Class". Here is the key paragraph:=20

"Some STL classes contain nested classes. These classes can not be
exported. For instance, deque contains a nested class deque::iterator.
If you export deque, you will get a warning that you must export
deque::iterator. If you export deque::iterator, you get a warning that
you must export deque. This is caused by a designed limitation that once
a template class is instantiated, it can not be re-instantiated and
exported. The only STL container that can currently be exported is
vector. The other containers (that is, map, set, queue, list, deque) all
contain nested classes and cannot be exported."

So if you want to use methods such as Category::getCurrentCategories(),
do them in a helper class that is linked as part of the DLL. I added
what I needed to the SimpleConfigurator (what I needed to do was delete
previously defined appenders from all categories before reloading a
config file, so it made sense in any case to put it there.)

Regards,=20

David Resnick=20
MobileSpear Inc.=20

Re: [Log4cpp-devel] multithread question

[Bastiaan B. <Bas...@li...>]

Hi Emiliano,

log4cpp 0.2.x does not explicitly support multithreading.
But with some restrictions it still can be used in a multithreading
environment:
* don't change your logging configuration when you have multiple threads
running. In most cases you'll setup your Category hierarchy before the
application starts logging anyway, so this is not a large problem. Calls
to setPriority() are still permitted.
* The append function must be atomic. Log4cpp's appenders have been
written in a way that requires only 1 call to the underlying system to
write a log message (i.e. a single write() for the FileAppender). If
your OS handles this atomically, the logfile will be OK. Otherwise you
could end up with intertwined log messages. The latter appears to be the
case at least with OstreamAppender on Win32 platforms.

If you want to have full MT support, you'll be happy to know that as of
version 0.3.0 log4cpp includes code for multithreading. Currently
(release 0.3.2rc1) it supports Omnithreads and Win32 threads, but
support for POSIX threads should not be too difficult to add: it
requires an adapter implementation for a simple Mutex, ScopedLock and
ThreadLocalData. You're very welcome to help in this area, if you like.

Regards,

Bastiaan Bakker
LifeLine Networks bv
 =20

On Tue, 2002-06-18 at 18:05, Emiliano Martin wrote:
> Hi:
>=20
> I've read log4ccp does not suppport multithreading,  can i do something=20
> like this to assure atomic access=BF=BF
> or it's very restrictive?? (or stupid)
>=20
>=20
> void Category::_logUnconditionally(Priority::Value priority,
>                                       const char* format,
>                                       va_list arguments) throw() {
>        OstringStream messageBuffer;
>=20
>        pthread_mutex_lock(writeMutex);
>        messageBuffer.vform(format, arguments);
>        _logUnconditionally2(priority, messageBuffer.str());
>        pthread_mutex_unlock(writeMutex);
>    }
>           =20
> thanks in advance
>=20
>=20
> -------------------------------------------------------------------------=
---
>                    Bringing you mounds of caffeinated joy
>                       >>>     http://thinkgeek.com/sf    <<<
>=20
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

[Log4cpp-devel] release 0.3.2rc1 on website

[Bastiaan B. <Bas...@li...>]

Hi,

For the convinience of people without CVS, I created a log4cpp-0.3.2rc1
tar ball and put it on the website, here:
http://log4cpp.sourceforge.net/releases/log4cpp-0.3.2rc1.tar.gz
This prerelease is not yet ready for general consumption (hence the
hidden directory), but please give it a try to check for any problems 
before a final 0.3.2 release.

New in this release is:

Support for Win32 threads added.
Added NTEventLogAppender.
Added Win32DebugAppender.
Fixed NDC context problem if depth > 2.
Added aclocal support.

Cheers,

Bastiaan

[Log4cpp-devel] multithread question

[Emiliano M. <emi...@te...>]

Hi:

I've read log4ccp does not suppport multithreading,  can i do something=20
like this to assure atomic access=BF=BF
or it's very restrictive?? (or stupid)


void Category::_logUnconditionally(Priority::Value priority,
                                      const char* format,
                                      va_list arguments) throw() {
       OstringStream messageBuffer;

       pthread_mutex_lock(writeMutex);
       messageBuffer.vform(format, arguments);
       _logUnconditionally2(priority, messageBuffer.str());
       pthread_mutex_unlock(writeMutex);
   }
          =20
thanks in advance

[Log4cpp-devel] multithread question

[Emiliano M. <emi...@te...>]

 Hi:

I've read log4ccp does not suppport multithreading,  can i do something=20
like this to assure atomic access=BF=BF
or it's very restrictive?? (or stupid)

=20
 void Category::_logUnconditionally(Priority::Value priority,
                                       const char* format,
                                       va_list arguments) throw() {
        OstringStream messageBuffer;
=20
        pthread_mutex_lock(writeMutex);
        messageBuffer.vform(format, arguments);
        _logUnconditionally2(priority, messageBuffer.str());
        pthread_mutex_unlock(writeMutex);
    }
            =20

thanks in advance

Re: [Log4cpp-devel] MS Threads & DLL Build patch merged, NTEventLogAppender added

[Bastiaan B. <Bas...@li...>]

Hi David,

Thanks for your work. I'll try to make a prerelease for 0.3.2 tonight,
to facilitate people without CVS.

Cheers,

Bastiaan

On Mon, 2002-06-17 at 10:43, David Resnick wrote:
> Hi all,
> 
> I've merged Aaron Ingram's patch for MS Threads and DLL build. I've also
> added a new appender, NTEventLogAppender. 
> 
> Here's a more detailed list of changes/additions, as written to the
> ChangeLog:
> 
> * Merge of MS Threads & DLL Build support patch by Aaron Ingram
> <ai...@ya...>
> with these changes:
> * src/main.cpp renamed to src/DllMain.cpp
> * Run-time library used for log4cppDLL changed to Multithreaded DLL
> (fixed need for #pragma warning(disable:4275))
> * pragma directives moved from various headers to
> include/log4cpp/Portability.hh.
> * include/log4cpp/threading/MSThreads.hh: reset(): TlsSetValue uses
> parameter value instead of deleted one.
>     
> * include/log4cpp/NTEventLogAppender.hh, src/NTEventLogAppender.cpp,
> msvc/NTEventLogAppender.mc, tests/testNTEventLog.cpp: added
> NTEventLogAppender.
>     
> * msvc/testMain/testMain.dsp, msvc/testNTEventLog/testNTEventLog.dsp
> added. 
> 
> Please checkout these changes and post any problems you encounter with
> them.
> 
> Regards, 
> 
> David Resnick 
> MobileSpear Inc. 
> 
> 
> _______________________________________________________________
> 
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

[Log4cpp-devel] MS Threads & DLL Build patch merged, NTEventLogAppender added

[David R. <dre...@mo...>]

Hi all,

I've merged Aaron Ingram's patch for MS Threads and DLL build. I've also
added a new appender, NTEventLogAppender.=20

Here's a more detailed list of changes/additions, as written to the
ChangeLog:

* Merge of MS Threads & DLL Build support patch by Aaron Ingram
<ai...@ya...>
with these changes:
* src/main.cpp renamed to src/DllMain.cpp
* Run-time library used for log4cppDLL changed to Multithreaded DLL
(fixed need for #pragma warning(disable:4275))
* pragma directives moved from various headers to
include/log4cpp/Portability.hh.
* include/log4cpp/threading/MSThreads.hh: reset(): TlsSetValue uses
parameter value instead of deleted one.
   =20
* include/log4cpp/NTEventLogAppender.hh, src/NTEventLogAppender.cpp,
msvc/NTEventLogAppender.mc, tests/testNTEventLog.cpp: added
NTEventLogAppender.
   =20
* msvc/testMain/testMain.dsp, msvc/testNTEventLog/testNTEventLog.dsp
added.=20

Please checkout these changes and post any problems you encounter with
them.

Regards,=20

David Resnick=20
MobileSpear Inc.=20

Re: [Log4cpp-devel] NDC bug fix for "MS Threads & DLL Build" patch

[Bastiaan B. <Bas...@li...>]

Hi David,

Thanks for the report. Since you are actually using Aaron's patch, would
you mind spending some time on merging it? Aaron didn't have time to do
it himself, and I don't want to blindly merge it myself without any way
to check it or fix problems (I don't have MSVC++). 
It should be too much work: just a merge to the CVS trunk and few
iterations of test builds and adaptions based on feed back.

Cheers,

Bastiaan

PS. Any other MSVC++ volunteers are welcome to help too of course!

PPS. David, your log4cpp-devel list address contains single quotes where
it shouldn't. This may cause your mail to bounce.
   

On Tue, 2002-06-11 at 16:28, David Resnick wrote:
> There is a bug in "MS Threads & DLL Build" patch that prevents NDCs from
> working. 
> 
> To fix it, in "include\log4cpp\threading\MSThreads.hh", line 155 change:
> 
>                 TlsSetValue(_key, thing);
> 
> To 
> 
>                 TlsSetValue(_key, p);
> 
> This hasn't been tested extensively; but it gets testNDC.cpp working.
> 
> Regards, 
> 
> David Resnick 
> MobileSpear Inc.
> 
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
> 
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

[Log4cpp-devel] NDC bug fix for "MS Threads & DLL Build" patch

[David R. <dre...@mo...>]

There is a bug in "MS Threads & DLL Build" patch that prevents NDCs from
working.=20

To fix it, in "include\log4cpp\threading\MSThreads.hh", line 155 change:

                TlsSetValue(_key, thing);

To=20

                TlsSetValue(_key, p);

This hasn't been tested extensively; but it gets testNDC.cpp working.

Regards,=20

David Resnick=20
MobileSpear Inc.

[Log4cpp-devel] RE: threads and a question

[charlie <buc...@ol...>]

> > Just thought I'd throw my $0.02 regarding threads. If seen pthreads
> > mentioned a couple of times in the archives, but no mention of using
> > pthreads with win32. There is a LGPL version of pthreads for
> win32 which is
> > quite good... http://sources.redhat.com/pthreads-win32/. I've
> been using it
> > extensively and it works quite well...
>
> Well, in that case I would like to invite you to write pthreads-win32
> support for log4cpp ;-)
> Actually since it is crossplatform I presume, that would mean pthreads
> support for *nix and other platforms as well. Hmm, very nice.

If I actually knew what I was doing I'd give it a try...problem is that I
wouldn't wish my threaded code on anyone right now...using exensively
doesn't mean using well in this case :-). But I think you got the
idea...pthreads IS cross platform between *nix, and the idea behind the
win32 port was to bring this to WinXX. The folks at Elvin
(http://elvin.dstc.edu.au/) use it as a cross platform threaded API. You
might want to throw a quesiton out on their development list to get their
thoughts...

> >
> > Now on to my big question...log4j includes level, appender and layout
> > "inheritance". log4cpp doesn't seem to support these features.
> Is this on
> > purpose? I would think this is a handy feature.
> >
>
> Maybe I don't understand your question, but I think you are saying that
> in log4j levels, appenders and layouts are inherited in the sense that a
> LoggingEvent sent to child Category (Logger) will be processed by the
> appender and layout of the parent Category.
> Well, log4cpp does this too, in pretty much the same way as log4j. Just
> look at the examples in the tests subdirectory.

Hummm....I did try all the examples, specifically testCategory.cpp for this
case, and it didn't seem to do what I expected. Is what you said true if the
parent is root? I will give it another go, and I'll send an example if it
seems to be doing something different...

VR, Charlie

Re: [Log4cpp-devel] threads and a question

[Bastiaan B. <bas...@li...>]

On Wed, 2002-06-05 at 05:56, charlie wrote:
> Hi,
> 
> Just thought I'd throw my $0.02 regarding threads. If seen pthreads
> mentioned a couple of times in the archives, but no mention of using
> pthreads with win32. There is a LGPL version of pthreads for win32 which is
> quite good... http://sources.redhat.com/pthreads-win32/. I've been using it
> extensively and it works quite well...

Well, in that case I would like to invite you to write pthreads-win32
support for log4cpp ;-) 
Actually since it is crossplatform I presume, that would mean pthreads
support for *nix and other platforms as well. Hmm, very nice.
 
 
> 
> Now on to my big question...log4j includes level, appender and layout
> "inheritance". log4cpp doesn't seem to support these features. Is this on
> purpose? I would think this is a handy feature.
> 

Maybe I don't understand your question, but I think you are saying that
in log4j levels, appenders and layouts are inherited in the sense that a
LoggingEvent sent to child Category (Logger) will be processed by the
appender and layout of the parent Category. 
Well, log4cpp does this too, in pretty much the same way as log4j. Just
look at the examples in the tests subdirectory.

Cheers,

Bastiaan

 
> VR, Charlie
> 
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> 
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

Re: [Log4cpp-devel] aclocal support

[Bastiaan B. <bas...@li...>]

On Mon, 2002-06-03 at 23:52, Cedric Le Goater wrote:
> Hello all,
> 
> I've commited a 'log4cpp.m4' file for aclocal support. The original file is 
> from glib/gtk, in which I just did a global replace. It uses the standard 
> configuration script 'log4cpp-config' to get the path values. They are no 
> code changes, just some Makefile improvements.
> 

Ah, very nice.

> I've been building and using Log4cpp rpms for a while now, with success.
> 
> Are there any plans/needs/restrictions on distributing binary log4cpp 
> packages on SourceForge ? Which plateforms would be the primary targets ? 
> which compilers ? gcc2/gcc3 ? What's your feeling about it ?

Well, for now I don't have any plans for binary packags myself. But I'm
not against distribution of binary packages built by others. With the
download stats we can easily see whether there's interest in them.
So if you have want to put log4cpp RPMs on sourceforge, be my guest and
go ahead! 

Cheers,

Bastiaan



> 
> 
> C.
> 
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> 
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

[Log4cpp-devel] threads and a question

[charlie <buc...@ol...>]

Hi,

Just thought I'd throw my $0.02 regarding threads. If seen pthreads
mentioned a couple of times in the archives, but no mention of using
pthreads with win32. There is a LGPL version of pthreads for win32 which is
quite good... http://sources.redhat.com/pthreads-win32/. I've been using it
extensively and it works quite well...

Now on to my big question...log4j includes level, appender and layout
"inheritance". log4cpp doesn't seem to support these features. Is this on
purpose? I would think this is a handy feature.

VR, Charlie

[Log4cpp-devel] aclocal support

[Cedric Le G. <leg...@fr...>]

Hello all,

I've commited a 'log4cpp.m4' file for aclocal support. The original file is 
from glib/gtk, in which I just did a global replace. It uses the standard 
configuration script 'log4cpp-config' to get the path values. They are no 
code changes, just some Makefile improvements.

I've been building and using Log4cpp rpms for a while now, with success.

Are there any plans/needs/restrictions on distributing binary log4cpp 
packages on SourceForge ? Which plateforms would be the primary targets ? 
which compilers ? gcc2/gcc3 ? What's your feeling about it ?


C.

RE: [Log4cpp-devel] ERROR collision on win32

[David R. <dre...@mo...>]

Thanks for the tips! (This one, and that from Aaron)

Obviously, including "Portability.hh" before "Priority.hh" did the trick
-- on 1 occasion.=20

In a different spot it didn't, but then #define NOGDI solved the
problem.

David Resnick


-----Original Message-----
From: Bastiaan Bakker [mailto:bas...@li...]=20
Sent: Tuesday, May 28, 2002 23:57
To: David Resnick
Cc: log...@li...
Subject: Re: [Log4cpp-devel] ERROR collision on win32

Hi David,=20

The preferred way of fixing this is by correcting the code that #defines
ERROR in the first place. Claiming such a common name as 'ERROR' in
through the preprocessor is quite rude and unnecessary.=20
For cases where this is not possible log4cpp contains a workaround which
can be enable by #defining LOG4CPP_FIX_ERROR_COLLISSION. On Win32
platforms this is the default (see include/log4cpp/config-win32.h), for
other platforms you need to arrange for it yourself.

Good luck,

Bastiaan Bakker

PS. And yes, Priority.hh mentions a FAQ, but it has not been written
yet.

=20
On Mon, 2002-05-27 at 13:59, David Resnick wrote:
> Hi all,
>=20
> I'm having problems using log4cpp::Priority::ERROR. When I just
include
> priority.hh, I get error messages telling me that ERROR is not
defined.
>=20
> Putting this:=20
>=20
> #ifdef ERROR
> #undef ERROR
> #endif
>=20
> before including priority.hh enables me to compile, but I'm sure there
> is a better way of fixing it (some define?).=20
>=20
> In Priority.hh there is mention of a FAQ, but I can't find it.
>=20
> What is the preferred way of fixing this problem?
>=20
> Regards,=20
>=20
> David Resnick=20
> MobileSpear Inc.=20
>=20
>=20
> _______________________________________________________________
>=20
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>=20
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

RE: [Log4cpp-devel] Large strings in cat.debug()

[Bastiaan B. <Bas...@li...>]

This looks like a limit in the snprintf() implementation on your =
platform. To work around it you can configure log4cpp to use an =
alternative snprint() implementation by removing the line
'#define LOG4CPP_HAVE_SNPRINTF 1' in include/log4cpp/config-win32.h

Good luck,

Bastiaan


> -----Original Message-----
> From: David R Robison [mailto:drr...@op...]
> Sent: Wednesday, May 29, 2002 2:04 PM
> To: Bastiaan Bakker; 'Aaron Ingram'
> Cc: log...@li...
> Subject: RE: [Log4cpp-devel] Large strings in cat.debug()
>=20
>=20
> I tried Testbench. It printed strings of length up to (and including)
> 128 characters just fine. However, it would not print strings=20
> of length
> 129 or greater. Note, however, this only applies when printing the
> strings as:
>=20
> log.error("%s", buffer);
>=20
> Any ideas?
>=20
> David R Robison
> Open Roads Consulting, Inc.
>=20
>=20
> -----Original Message-----
> From: Bastiaan Bakker [mailto:bas...@li...]=20
> Sent: Tuesday, May 28, 2002 6:09 PM
> To: David R Robison
> Cc: log...@li...
> Subject: Re: [Log4cpp-devel] Large strings in cat.debug()
>=20
> Hi David,
>=20
> Log4cpp does not have a maximum log string length. This sounds like a
> platform specific bug.=20
> The 'testbench' utility in the tests subdirectory is a simple=20
> way to try
> strings of arbitrary length: 'testbench 1 <length>'. Maybe it can help
> you to debug your problem.
>=20
> Good luck,=20
>=20
> Bastiaan Bakker
>=20
> =20
> On Tue, 2002-05-28 at 23:12, David R Robison wrote:
> > I'm trying to display a long string (~150bytes) using=20
> log4cpp V0.3.1.
> > The code is
> > =20
> > Cat.debug("CMD: %s (%d)", cmd, strlen(cmd));
> > =20
> > If I shorten the string cmd to 10 characters, then it prints
> correctly.
> > If, however, the string is long, then only the DEBUG tag prints. Is
> > there some maximum to the length of a string with the %s flag? Is
> there
> > a way around this?=20
> >=20
> >=20
> > Any help would be appreciated.
> > =20
> > Ps. I'm using BCB4 on NT4
> > =20
> > David R Robison
> > Open Roads Consulting, Inc.
> > =20
>=20
>=20
>=20
>=20

RE: [Log4cpp-devel] Large strings in cat.debug()

[David R R. <drr...@op...>]

I tried Testbench. It printed strings of length up to (and including)
128 characters just fine. However, it would not print strings of length
129 or greater. Note, however, this only applies when printing the
strings as:

log.error("%s", buffer);

Any ideas?

David R Robison
Open Roads Consulting, Inc.


-----Original Message-----
From: Bastiaan Bakker [mailto:bas...@li...] 
Sent: Tuesday, May 28, 2002 6:09 PM
To: David R Robison
Cc: log...@li...
Subject: Re: [Log4cpp-devel] Large strings in cat.debug()

Hi David,

Log4cpp does not have a maximum log string length. This sounds like a
platform specific bug. 
The 'testbench' utility in the tests subdirectory is a simple way to try
strings of arbitrary length: 'testbench 1 <length>'. Maybe it can help
you to debug your problem.

Good luck, 

Bastiaan Bakker

 
On Tue, 2002-05-28 at 23:12, David R Robison wrote:
> I'm trying to display a long string (~150bytes) using log4cpp V0.3.1.
> The code is
>  
> Cat.debug("CMD: %s (%d)", cmd, strlen(cmd));
>  
> If I shorten the string cmd to 10 characters, then it prints
correctly.
> If, however, the string is long, then only the DEBUG tag prints. Is
> there some maximum to the length of a string with the %s flag? Is
there
> a way around this? 
> 
> 
> Any help would be appreciated.
>  
> Ps. I'm using BCB4 on NT4
>  
> David R Robison
> Open Roads Consulting, Inc.
>  

Re: [Log4cpp-devel] Large strings in cat.debug()

[Aaron I. <ai...@ya...>]

I haven't seen this problem before, but try downloading the latest cvs
source from sourceforge to see if that solves your problem.
Also, try building and running one of the testXXX programs that come
with the source code.  Do they work?  What happens if you lengthen one
of the output strings as you mention below?
Let me know how it goes.
-Aaron
aingram at users.sourceforge.net

--- David R Robison <drr...@op...> wrote:
> I'm trying to display a long string (~150bytes) using log4cpp V0.3.1.
> The code is
>  
> Cat.debug("CMD: %s (%d)", cmd, strlen(cmd));
>  
> If I shorten the string cmd to 10 characters, then it prints
> correctly.
> If, however, the string is long, then only the DEBUG tag prints. Is
> there some maximum to the length of a string with the %s flag? Is
> there
> a way around this? 
> 
> 
> Any help would be appreciated.
>  
> Ps. I'm using BCB4 on NT4
>  
> David R Robison
> Open Roads Consulting, Inc.
>  
> 


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: [Log4cpp-devel] Large strings in cat.debug()

[Bastiaan B. <bas...@li...>]

Hi David,

Log4cpp does not have a maximum log string length. This sounds like a
platform specific bug. 
The 'testbench' utility in the tests subdirectory is a simple way to try
strings of arbitrary length: 'testbench 1 <length>'. Maybe it can help
you to debug your problem.

Good luck, 

Bastiaan Bakker

 
On Tue, 2002-05-28 at 23:12, David R Robison wrote:
> I'm trying to display a long string (~150bytes) using log4cpp V0.3.1.
> The code is
>  
> Cat.debug("CMD: %s (%d)", cmd, strlen(cmd));
>  
> If I shorten the string cmd to 10 characters, then it prints correctly.
> If, however, the string is long, then only the DEBUG tag prints. Is
> there some maximum to the length of a string with the %s flag? Is there
> a way around this? 
> 
> 
> Any help would be appreciated.
>  
> Ps. I'm using BCB4 on NT4
>  
> David R Robison
> Open Roads Consulting, Inc.
>  

Re: [Log4cpp-devel] ERROR collision on win32

[Bastiaan B. <bas...@li...>]

Hi David, 

The preferred way of fixing this is by correcting the code that #defines
ERROR in the first place. Claiming such a common name as 'ERROR' in
through the preprocessor is quite rude and unnecessary. 
For cases where this is not possible log4cpp contains a workaround which
can be enable by #defining LOG4CPP_FIX_ERROR_COLLISSION. On Win32
platforms this is the default (see include/log4cpp/config-win32.h), for
other platforms you need to arrange for it yourself.

Good luck,

Bastiaan Bakker

PS. And yes, Priority.hh mentions a FAQ, but it has not been written
yet.

 
On Mon, 2002-05-27 at 13:59, David Resnick wrote:
> Hi all,
> 
> I'm having problems using log4cpp::Priority::ERROR. When I just include
> priority.hh, I get error messages telling me that ERROR is not defined.
> 
> Putting this: 
> 
> #ifdef ERROR
> #undef ERROR
> #endif
> 
> before including priority.hh enables me to compile, but I'm sure there
> is a better way of fixing it (some define?). 
> 
> In Priority.hh there is mention of a FAQ, but I can't find it.
> 
> What is the preferred way of fixing this problem?
> 
> Regards, 
> 
> David Resnick 
> MobileSpear Inc. 
> 
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> 
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

[Log4cpp-devel] Large strings in cat.debug()

[David R R. <drr...@op...>]

I'm trying to display a long string (~150bytes) using log4cpp V0.3.1.
The code is
 
Cat.debug("CMD: %s (%d)", cmd, strlen(cmd));
 
If I shorten the string cmd to 10 characters, then it prints correctly.
If, however, the string is long, then only the DEBUG tag prints. Is
there some maximum to the length of a string with the %s flag? Is there
a way around this? 


Any help would be appreciated.
 
Ps. I'm using BCB4 on NT4
 
David R Robison
Open Roads Consulting, Inc.
 

[Log4cpp-devel] ERROR collision on win32

[David R. <dre...@mo...>]

Hi all,

I'm having problems using log4cpp::Priority::ERROR. When I just include
priority.hh, I get error messages telling me that ERROR is not defined.

Putting this:=20

#ifdef ERROR
#undef ERROR
#endif

before including priority.hh enables me to compile, but I'm sure there
is a better way of fixing it (some define?).=20

In Priority.hh there is mention of a FAQ, but I can't find it.

What is the preferred way of fixing this problem?

Regards,=20

David Resnick=20
MobileSpear Inc.=20

[Log4cpp-devel] date-format configurable

[Thomas P. <tho...@os...>]

I used the %d format string for date output.
Is it possible to specify another layout than the 
default date string 

"Wed May 15 08:48:59 2002" via the library ?

I think the current output is okay, but our company
use another "styleguide" .

thomas

-- 

Re: [Log4cpp-devel] Porting of log4cpp 0.3.1 for thread of ACE library 5.2

[Bastiaan B. <bas...@li...>]

Hi Marco,

Thanks for your contribution. I'll add the AceThreads files, but someone 
using Ace and with a little knowledge of autoconf will need to help with 
the integration. Do you know whether Ace has autoconf macros, tha should 
make ik much easier to fit it in.
Also I noticed you added 'const' to the maxFileSize and maxBackupIndex 
parameters. Doe Sun CC need this for all parameters with defaults?

Cheers,

Bastiaan

Marco Villani wrote:

>Porting of log4cpp 0.3.1 for thread of ACE library 5.2
>(http://www.cs.wustl.edu/~schmidt/ACE.html).
>
>Environment: SunOs 5.6 with Forte 6.1 (Sun CC 5.2).
>
>I do not know automake, autoconf, m4, etc.
>I have modified .\src\makefile and .\tests\makefile.
>
>File list:
>.\config.log                                 Generated automatically by configure.
>.\log4cpp-config                             Generated automatically by configure.
>.\log4cpp.log                                Generated automatically by configure; log of initial error (read line 330).
>.\Makefile                                   Generated automatically by configure.
>.\config\Makefile                            Generated automatically by configure.
>.\include\config.h                           Generated automatically by configure.
>.\include\Makefile                           Generated automatically by configure.
>.\include\stamp-h                            Generated automatically by configure.
>.\include\log4cpp\config.h                   Generated automatically by configure.
>.\include\log4cpp\Makefile                   Generated automatically by configure.
>.\include\log4cpp\RollingFileAppender.hh     Small correction for Sun CC 5.2.
>.\include\log4cpp\threading\AceThreads.hh    ADDED.
>.\include\log4cpp\threading\Makefile         Generated automatically by configure.
>.\include\log4cpp\threading\Threading.hh     MODIFIED.
>.\src\Makefile                              HANDMADE to solve error at line 330 of .\log4cpp.log.
>.\src\Makefile.am                            HANDMADE to solve error at line 330 of .\log4cpp.log (??? useless ???)
>.\tests\Makefile                             HANDMADE to solve error at line 330 of .\log4cpp.log.
>.\tests\testFilter.cpp                       Small correction for Sun CC 5.2.
>.\tests\testmain.000.cpp                     ADDED FOR TEST.
>.\tests\testmain.001.cpp                     ADDED FOR TEST.
>.\tests\testmain.005.cpp                     ADDED FOR TEST.
>.\tests\testmain.006.cpp                     ADDED FOR TEST.
>.\tests\testmain.007.cpp                     ADDED FOR TEST.
>.\tests\testmain.008.cpp                     ADDED FOR TEST.
>.\tests\testmain.cpp                         MODIFIED FOR TEST.
>
>I have compiled all tests.
>All tests run successfully.
>
>I hope that these files could be useful for you.
>(See attached file: l4c_ace.tar.gz)
>
>Best regards.
>
>Marco Villani
>

[Log4cpp-devel] Porting of log4cpp 0.3.1 for thread of ACE library 5.2

[Marco V. <mar...@ma...>]

Porting of log4cpp 0.3.1 for thread of ACE library 5.2
(http://www.cs.wustl.edu/~schmidt/ACE.html).

Environment: SunOs 5.6 with Forte 6.1 (Sun CC 5.2).

I do not know automake, autoconf, m4, etc.
I have modified .\src\makefile and .\tests\makefile.

File list:
.\config.log                                 Generated automatically by configure.
.\log4cpp-config                             Generated automatically by configure.
.\log4cpp.log                                Generated automatically by configure; log of initial error (read line 330).
.\Makefile                                   Generated automatically by configure.
.\config\Makefile                            Generated automatically by configure.
.\include\config.h                           Generated automatically by configure.
.\include\Makefile                           Generated automatically by configure.
.\include\stamp-h                            Generated automatically by configure.
.\include\log4cpp\config.h                   Generated automatically by configure.
.\include\log4cpp\Makefile                   Generated automatically by configure.
.\include\log4cpp\RollingFileAppender.hh     Small correction for Sun CC 5.2.
.\include\log4cpp\threading\AceThreads.hh    ADDED.
.\include\log4cpp\threading\Makefile         Generated automatically by configure.
.\include\log4cpp\threading\Threading.hh     MODIFIED.
.\src\Makefile                              HANDMADE to solve error at line 330 of .\log4cpp.log.
.\src\Makefile.am                            HANDMADE to solve error at line 330 of .\log4cpp.log (??? useless ???)
.\tests\Makefile                             HANDMADE to solve error at line 330 of .\log4cpp.log.
.\tests\testFilter.cpp                       Small correction for Sun CC 5.2.
.\tests\testmain.000.cpp                     ADDED FOR TEST.
.\tests\testmain.001.cpp                     ADDED FOR TEST.
.\tests\testmain.005.cpp                     ADDED FOR TEST.
.\tests\testmain.006.cpp                     ADDED FOR TEST.
.\tests\testmain.007.cpp                     ADDED FOR TEST.
.\tests\testmain.008.cpp                     ADDED FOR TEST.
.\tests\testmain.cpp                         MODIFIED FOR TEST.

I have compiled all tests.
All tests run successfully.

I hope that these files could be useful for you.
(See attached file: l4c_ace.tar.gz)

Best regards.

Marco Villani